title: Closing a client socket , after server has already closed it's side
body: <p>(<code>Winsock32</code> / <code>C++</code> / <code>Win32</code> environment)</p>
  
  <p>To my understanding, as opposed to closing a file handle for instance (using <code>CloseHandle()</code>), 
  closing a socket is an operation of 2 parts, other then releasing the <code>SOCK</code> handle, and freeing the actual resource, it also responsible of informing the other side of the connection upon session termination. </p>
  
  <p>The question is, how to handle the scenario of a server closing the connection for it's own reason ,  and then client trying to close it on their side. That means, how to do only the resources releasing part, as described above , without the termination informing. </p>