@pervognsen "Want" is a strong word here, though. Not being able to dequeue an IOCP because someone else did isn't an error, you just loop.
-
-
Replying to @cmuratori
@cmuratori So you'd loop an WFMO on an IOCP then try to do a zero timeout GetQueuedCompletionStatus?2 replies 0 retweets 0 likes -
Replying to @pervognsen
@pervognsen Exactly. Really the best thing would be waiting on two IOCPs at once, but that's a separate issue.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@pervognsen The reasoning here is that Window has many things (message queue, OpenGL, etc.) that are thread-locked.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@pervognsen And with IOCP alone it is impossible to target a _specific_ thread with a message.1 reply 0 retweets 0 likes -
Replying to @cmuratori
@cmuratori@pervognsen The best thing would be one IOCP queue for everything and then one IOCP queue per thread for "special" things.1 reply 0 retweets 0 likes
@cmuratori @pervognsen But in the Win32 API as it stands, that's not possible AFAIK.
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.