WASP IV 64 Bit ⏳
WASP IV 64 Bit Instead, I'm getting a WSAEWOULDBLOCK error from the AcceptEx() call. I've tried it with and without the socket options, but it always comes out as WSAEWOULDBLOCK. Any thoughts? Or, perhaps there's a better way to check for data available in the socket without blocking? A: I solved this issue by using my socket's HOLD_OPTIONS (e.g. HOLD_CANCEL_OPTION) flags instead of the AI_* flag I was using ( For example, if I set the flags with the socket(), this is what I see in the Windows Event Log: ReceiveAsync succeeded (WSA_IO_PENDING) Seconds to receive? [0.000 (0 seconds left) This is not an exact call-to-action, but it's the best I could come up with to solve this issue ( I'm going
Read More