19 Jun
2023
19 Jun
'23
8:32 p.m.
On Sun Jun 18 04:54:34 2023 +0000, Ally Sommers wrote:
No; making the client socket nonblocking with `ioctlsocket()` causes it to instantly return with `WSAEWOULDBLOCK`. [Microsoft's documentation](https://learn.microsoft.com/en-us/windows/win32/winsock/windows-sockets-erro...) notes:
It is normal for WSAEWOULDBLOCK to be reported as the result from
calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
At least for TCP sockets it connects anyway, though. Basically they return WSAEWOULDBLOCK instead of WSAEINPROGRESS for some reason but the behaviour is the same. Is it different for AF_UNIX?