From: gah@ugcs.caltech.edu   
      
   Ersek, Laszlo  wrote:   
   > [-- text/plain, encoding 8bit, charset: iso-8859-2, 71 lines --]   
   > On Tue, 26 Oct 2010, David Schwartz wrote:   
   >> On Oct 25, 12:27 pm, Albert Manfredi  wrote:   
      
   >>> 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.   
   (snip)   
      
   >> Sadly, the use of the term "socket" is not consistent. For example, if   
   >> a process that has a socket for a TCP endpoint fork's, do the two new   
   >> processes each have a socket for the same endpoint? Or do the two file   
   >> descriptors reference the same socket?   
      
   > I think:   
      
   > file descriptor -> file description -> file (which is a socket)   
      
   For unix, and unix-like systems, file descriptors and sockets use   
   the same address space.  For others, I believe Windows (unless it   
   changed when I wasn't looking) they use a different address space.   
      
   For unix, one can use read and write on sockets, where for others   
   one must use send and recv.  (This is especially convenient in the   
   case of inetd.)   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)