ConnectTimeout should also cancel the handshake/initialization procedure when the server stopped responding #3
Description
When the TCP socket is open, but the server is not responding (wrong port or server process is paused/broken) the ConnectTimeout should still have an effect.
Currently, the server is waiting forever for a response.
Maybe use the builtin ReceiveTimeout and disable it as soon as the connection is initialized?
Add a separate ProtocolTimeout/HandshakeTimeout/whatever property to the connect parameters?