ba9b8492   
   From: gah@ugcs.caltech.edu   
      
   Albert Manfredi  wrote:   
   > On Oct 25, 1:28 pm, Rick Jones  wrote:   
      
   >> Not with any implementation of "sockets" I've seen.  A "socket" is an   
   >> interface between the user and the underlying protocol.  In the case   
   >> of TCP and sockets, each distinct TCP connection (four tuple of   
   >> local/remote IP, local/remote port) will be a distinct socket.   
      
   > At the risk of sounding overly pedantic, the socket is usually   
   > described as a five-tuple, I think. In addition to IP addresses and TC   
   > ports, there is also the protocol ID.   
      
   As I understand it, "socket" is part of a specific API for TCP/IP,   
   though a popular one.  The OP specifically asked about TCP, though.   
   And UDP is different.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)