XPost: comp.arch.embedded, comp.os.linux.networking   
   From: pfeiffer@cs.nmsu.edu   
      
   Paul Keinanen  writes:   
      
   > On Sat, 20 Feb 2010 08:15:13 -0800 (PST), karthikbalaguru   
   >  wrote:   
   >   
   >>   
   >>Agreed, but the query is about the design of the   
   >>TCP server and the UDP server. In TCP server   
   >>whenever a new connection arrives, it accepts the   
   >>connection and invokes a new process to handle   
   >>the new connection request. The main point here   
   >>is that 'a new process is created to handle every   
   >>new connection that arrives at the server' .   
   >>In the case of UDP server, it seems that most   
   >>of the the server design is such that there is only   
   >>one process to handle various clients.   
   >>Will the TCP server get overloaded if it creates   
   >>a new process for every new connection ? How is   
   >>it being managed ?   
   >   
   > As long as you have a simple transaction system, one incoming request,   
   > one outgoing response, why on earth would any sensible person create a   
   > TCP/IP connection for this simple transaction ?   
      
   To avoid having to deal with dropped/corrupted packets yourself.   
      
   --   
   As we enjoy great advantages from the inventions of others, we should   
   be glad of an opportunity to serve others by any invention of ours;   
   and this we should do freely and generously. (Benjamin Franklin)   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)