> 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.
> 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.
