Re: select()/poll() on Win32: possible funding, but is it insane?
[email protected] (Mark Mielke)
| Newsgroups | perl.perl5.porters,perl.loop |
|---|---|
| Message-ID | <[email protected]> |
On Wed, Jan 31, 2001 at 07:13:43AM -0500, "Horsley Tom" wrote: > > Too bad it can only wait on 32 or 64 handles, eh? > That depends on what MAXIMUM_WAIT_OBJECTS is defined in the MS headers. > If it really is as small as 64, that seems a little on the pitiful > side, but I've never run into a problem with it. It is defined as 32 on some platforms, although I believe that underneath it is 64 everywhere. > > Also it doesn't work for pipes, and if memory serves, it > > doesn't really work for sockets. > Nope, it works fine for everything, but if you use it with some kind of > handle that is always ready, then, naturally, it will never wait > on it :-). The key to using ir for most I/O type operations is to > associate an event handle with a specific read or write request, > then wait on that event, not on the handle for the I/O device. I've > got tons of code that does this with sockets, and it all works fine > on every win32 platform. I can't get pipe's to work in asynchronous mode for WinME. The documentation says it won't. WinNT may be a different story. mark -- [email protected]/[email protected]/[email protected] __________________________ . . _ ._ . . .__ . . ._. .__ . . . .__ | SIR Tools (7H12) |\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ | Nortel Networks | | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada One ring to rule them all, one ring to find them, one ring to bring them all and in the darkness bind them... http://mark.mielke.cc/