On Fri Jun 16 17:31:25 2023 +0000, Zebediah Figura wrote:
Do we need to bother with the client thread here? (Could we potentially make the client socket nonblocking instead?)
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.