What is supposed to happen if a server wants to bind() to a port   
   which happens to already be in use by a TCP session?   
      
   Since the TCP session is identified by the quad source address,   
   source port, destination address, destination port, that should not   
   limit the ability to bind() to that port.  But is that what   
   really happens on real systems?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)