c2523f52   
   XPost: comp.arch.embedded, comp.os.linux.networking   
   From: keinanen@sci.fi   
      
   On Sat, 20 Feb 2010 05:10:54 -0800 (PST), karthikbalaguru   
    wrote:   
      
   >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 ?   
      
   While I understand that some lazy programmers might use TCP/IP for   
   some minor ad hoc applications.   
      
   I still do not understand why anybody would use TCP/IP for any   
   critical 24x7 applications.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)