If my client\'s connection is broken on the other end( kill -9 server)
. It takes several minutes for the client to determine that something is wrong. Sock
Maybe the SendTimeout
and/or ReadTimeout
properties of the Socket
could help?
Have you tried to set a shorter connection timeout ?
Spawn another thread that is constantly pinging the server - really the best you can do since a socket is not an active connection.
I refer you to my answer to your C++ version of this question...
This seems to work for me... Does anyone see any issues?
public bool IsConnected
{
get {return !(Socket.Poll(1, SelectMode.SelectRead)
&& m_socket.Available ==0)}
}
Can also be put into an extension method.
public static class SocketExtensions
{
public static bool IsConnected(this Socket @this)
{
return !(@this.Poll(1, SelectMode.SelectRead) && @this.Available == 0);
}
}
Now you can easily use it in your code dealing with sockets.
var mySocket = new Socket();
while(mySocket.IsConncted())
{
// Do Stuff
}
Try checking the Available property, it should throw a SocketException
when the connection has been closed.
Source
Edit, here is how you would use it:
while(socket.Connected)
{
try
{
while (socket.Available == 0)
System.Threading.Thread.Sleep(100); // Zzzz
}
catch (SocketException)
{
// connection closed
// do something
}
/* Do some processing */
}
You could also try using the Poll
method.
From Source:
Alternatively, you can also utilize the Poll() Socket method with the SelectRead SelectMode parameter. This method will return a true value if data is available or if the connection has been closed by the remote host. You will then need to differentiate between which of these situations has occurred (by reading the socket buffer, and seeing if it returns a zero value).