On Nov 12, 2003, at 10:47 AM, Itamar Shtull-Trauring wrote:
On Wed, 12 Nov 2003 01:56:25 -0500 Glyph Lefkowitz <glyph@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.
Signals need a whole different approach because signals do not wake up CFRunLoop, so when you install handlers it wakes up once a second anyway. The correct solution is to use a mach port waker for signals, I have not implemented this yet because there are no mach port facilities available from Python yet (I looked into it, but doing mach ports use a lot of C macros, so it would be hard). When is next release planned? -bob