C#

// in your NetworkServer class
private volatile bool quit = false;
private ReaderWriterLock rwl = new ReaderWriterLock();

// in OnClientConnect
Socket clientSocket = null;
rwl.AcquireReaderLock(-1);// -1 == Timeout.Infinite
try
{
  if ( quit ) return;
  clientSocket = serverSocket.EndAccept(state);
}
finally
{
  rwl.ReleaseReaderLock();
}

// same ( reader lock ) in OnClientRead - wrap the call to EndReceive

// in Shutdown
rwl.AcquireWriterLock(-1);
try
{
  quit = true;

  foreach ( var client in clientList )
  {
    client.Socket.Shutdown();
    client.Socket.Dispose();
  }
}
finally
{
  rwl.ReleaseWriterLock();
}

----------------------------------
Be excellent to each other

Metal76 wrote:

and let you know

----------------------------------
Be excellent to each other

try
{
    ... 
    // Starts receiving data
    _Socket.BeginReceive(_ReceiveBuffer,
                          0,
                         _ReceiveBuffer.Length,
                           SocketFlags.None,
                          new AsyncCallback(ClientReceiveCallback),
                           null);
    ...

}
catch (SocketException sockExc)
{
    // Process connection errors (e.g. connection closed by peer...)
    // by closing the socket 
    SocketClose((SocketError)sockExc.ErrorCode);
}
catch (ObjectDisposedException objDispExc)
{
    // Could fire during forced shutdown because 
    // socket is disposed while reception is pending
    // No need to close the socket here
}

Metal76 wrote:

I feel a little uneasy to use exceptions to implement normal programming logic, but I could not find a "clean" way to forcibly shutdown sockets

Mark Salsbery
Microsoft MVP - Visual C++