On Fri, Apr 8, 2011 at 6:26 PM, Glyph Lefkowitz <gl...@twistedmatrix.com> wrote: > > On Apr 8, 2011, at 2:56 AM, Tristan Seligmann wrote: > >> On Fri, Apr 8, 2011 at 4:52 AM, Kevin Horn <kevin.h...@gmail.com> wrote: >>> Note that you can wait on more than 64 objects at a time, just not using a >>> single WaitForMultipleObjects call. The MSDN page Glyph pointed out has a >>> little more info. >> >> The proposed solutions, however, seem rather unsatisfactory. If you're >> going to start spawning new threads to monitor everything, you might >> as well just do IOCP in another thread, or even in the main thread (at >> least as far as I know). > > I think we may be close to the point where we can drop win32eventreactor > completely. I think IOCP can deal with arbitrary Windows events too, so if > we just expose that in a compatible way, and whatever else comes along with > it, we can just delete win32er without losing any functionality. (Or maybe > we already do? Not my area of expertise any more :)).
It's technically possible, but it's not a thing that iocpreactor currently does. Someone (hurr hurr) needs to stop slacking and implement it, along with support for waiting on an arbitrary number of handles. Also, how much do we care that win32er can be used without a compiler, but iocpreactor needs one to build the API wrapper? _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
