XPost: comp.arch.embedded, comp.os.linux.networking   
   From: sp4mtr4p.boudewijn@indes.com   
      
   Op Thu, 25 Feb 2010 03:41:07 +0100 schreef Maxwell Lol   
   :   
   > karthikbalaguru  writes:   
   >> While reading about the various designs, interestingly i   
   >> came across an info that the design of TCP servers is   
   >> mostly such that whenever it accepts a connection,   
   >> a new process is invoked to handle it .   
   >> But, it seems that in the case of UDP servers design,   
   >> there is only a single process that handles all client   
   >> requests. Why such a difference in design of TCP and   
   >> UDP servers ? How is TCP server able to handle   
   >> large number of very rapid near-simultaneous connections ?   
   >> Any ideas ?   
   >   
   >   
   > The TCP server forks a new process (which is very fast, as nothing   
   > needs to to copied)   
      
   Some things need to be copied, like file descriptors, but nothing big.   
   Still, forking takes considerably more overhead in time and space than   
   managing the context yourself.   
      
      
      
   --   
   Gemaakt met Opera's revolutionaire e-mailprogramma:   
   http://www.opera.com/mail/   
   (remove the obvious prefix to reply by mail)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)