@cmuratori Or perhaps asking the question from a different angle, is there any discussion about why you can't wait on > 1 IOCP handle?
Is there any historical information out there I can read that discusses why IOCP handles can't participate in WaitForMultipleObjects et al?
-
-
-
@cmuratori I'm assuming there was a specific kernel performance or complexity reason for it but I'm not sure what it would be. - Show replies
New conversation -
-
-
@cmuratori doesn't WaitForMultipleObjects() have 64 handle limit and odd behaviour of returning index of handle which triggered event? -
@binarycrusader Not sure what that has to do with my question? - Show replies
New conversation -
-
-
@cmuratori You can only Wait* on objects that signal themselves. IOCPs have no well-defined 'signalled' state so they never set the flag. -
@cmuratori At least that's my understanding of it, but I don't know bupkis. - Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.