Hi, I'm having some trouble understanding non-blocking socket operations.
If I have a non-blocking server (select based) and use a non-blocking send from the client, select will "wake up" and the server will have a chance to check which socket in the set is ready to receive info. But since both the client and server is non-blocking wouldn't the client send() return an error and set the errorcode to WSAEWOULDBLOCK (or EWOULDBLOCK depending on the system..) during the time it takes for the server to start its recv()?