[Twisted-Python] win32 event loop

Andrew Bennetts andrew-twisted at puzzling.org
Mon May 6 20:48:43 EDT 2002


On Mon, May 06, 2002 at 07:29:32PM +0300, Itamar Shtull-Trauring wrote:
> 
> So I've done some research, and it looks like I/O Completion ports are the 
> way to go for scalable networking. This will probably mean rewriting (or 

That is also what I understand to be the case on Windows.

> subclassing) the stuff in tcp.py and abstract.py, since this the Proactor 
> pattern, not the Reactor pattern, so things work a bit differently. I'm not 
> even sure how UDP is done, but that's something I'll worry about later.
> 
> [Subtext: Microsoft create more useless work for me]

As far as I can tell, there's currently no way to use I/O Completion
ports from Python.

Have you got any sample code or something which can do this?  Otherwise
I guess we're stuck with writing an extension module.  Bleagh.

I recall reading that Apache 1.x used up to 64 threads doing WFMO, that
would then trigger a central WFMO -- so perhaps it's not that bad.  No
idea what Apache 2 does.  Certainly, only one level of nesting is enough
-- 64 * 64 sockets should be enough for anybody ;)

-Andrew.





More information about the Twisted-Python mailing list