Does Windows support socket timeouts?

[fpagliughi]

In the stream_socket class, the calls to read_timeout() and write_timeout() are empty for Windows. I can't remember if Windows doesn't support this, or if I was just too lazy to look up how.

@borrrden Do you know?

bool stream_socket::read_timeout(const microseconds& to)
{
    #if !defined(_WIN32)
        timeval tv = to_timeval(to);
        return set_option(SOL_SOCKET, SO_RCVTIMEO, tv);
    #else
        return false;
    #endif
}

[borrrden]

Not in the same way, I think. It does support read and write timeouts but they are set per socket (i.e. setsockopt) while it looks like this is being set globally.

[fpagliughi]

Oh, sorry that code snippet is a bit misleading. The set_option() call is a socket member function, so it changes the timeout for the specific socket.

It just calls the OS setsockopt(). Does Windows support that? Looks like maybe. So perhaps I remove the conditional compilation and it works. I'll try that when I dust off the Windows laptop.

[borrrden]

Yes, setsockopt is a part of the WSA API.

[fpagliughi]

Yes, the same call... except that Windows uses a different data type for the parameter! (DWORD milliseconds instead of timeval). OMG. Windows.