[Twisted-Python] Re: [Twisted-commits] Somehow the waker still messes up cfreactor, never installing waker for now

[Itamar Shtull-Trauring]

On Wed, 12 Nov 2003 01:56:25 -0500
Glyph Lefkowitz <glyph at twistedmatrix.com> wrote:

> However, "really slow" doesn't quite describe the problem.  A server 
> which sends an event to a thread without a waker and then receives a 
> callFromThread may never wake up, if there isn't more network activity
> 
> happening.

Yep, a reactor without a waker is essentially broken. It'll also break
the SIGCHILD handler in CVS. Please do try to find a solution before our
next release.

-- 
Itamar Shtull-Trauring    http://itamarst.org/
Available for Python & Twisted consulting