Ok, I think I'm starting to get what's going on here on my windows
box:
1) We try to connect non-blocking
2) There is no immediate error so an EWOULDBLOCK is thrown
3) The connection attempt magically continues in the background
4) We loop around and try to connect again
5) The process may be
On Mar 3, 2:11 pm, Steve unetright.thebas...@xoxy.net wrote:
What should happen in my opinion is that at some point we should go
from getting WSAEINVALID back to a single EWOULDBLOCK when the first
connection is refused and then a brand new connection is started. But
we never do see that.
On Tuesday 03 March 2009 22:11:11 Steve wrote:
The real problem is we need a way to set a timeout on the connection
attempt in the background without making it blocking.
Yes, this is what I've done :-)
OK, not without sucking CPU, but I did say The cost at present is higher
CPU usage than
