t-delegated.example.com> 5d6cbc59   
   From: rick.jones2@hp.com   
      
   Barry Margolin  wrote:   
   > The main problem with this is that it requires the server to reserve   
   > resources for the connection (e.g. fork a server process) before it's   
   > sure that the connection has been established.   
      
   99 times out of ten, the connection is fully established before   
   accept() is called right?  Thus any application fork() call would be   
   after the new connection was in the ESTABLISHED state.  Now, a stack   
   might offer the option of an "eager" or "early" connection   
   notification, but that isn't relaly the norm.   
      
   rick jones   
   --   
   firebug n, the idiot who tosses a lit cigarette out his car window   
   these opinions are mine, all mine; HP might not want them anyway... :)   
   feel free to post, OR email to rick.jones2 in hp.com but NOT BOTH...   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)