79b567ad   
   From: michael.podolsky.69@gmail.com   
      
   Thanks for the explanation.   
      
   On Oct 18, 12:40 pm, Barry Margolin  wrote:   
      
   > If you want your sockets code to be portable, don't close the connection   
   > if you're not really done with it. Use shutdown() to send a FIN, and   
   > then just suck up any data that keeps arriving until the client closes   
   > the connection.   
      
   As for the portability and overall robust functionality, how would you   
   consider shutdowning just the sending side and   
   then immediately closing the socket, i.e:   
      
   //server side:   
   shutdown(socket, SHUT_WR);   
   close(socket);   
      
   which is supposed to allow the server not to read the rest of the   
   client's data?   
      
   Should it work correctly and reasonably? If not, why?   
      
   Regards, Michael   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)