XPost: comp.arch.embedded, comp.os.linux.networking   
   From: grahn+nntp@snipabacken.se   
      
   ["Followup-To:" header set to comp.protocols.tcp-ip.]   
      
   On Sat, 2010-02-20, Paul Keinanen wrote:   
   > 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   
   ...   
   >>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 continue in the same confrontational tone:   
      
   Because UDP doesn't work in practice except in some very limited   
   scenarios. This is also why almost no widely used application   
   protocols use UDP.   
      
   If you're arguing that UDP is generally a better transport protocol   
   than TCP, you're in a small minority.   
      
   I also note that it was you who brought up these simple transaction   
   systems. It's not implied in the text you quoted (although it does   
   make pointless comparisons between the internal workings of UDP and   
   TCP servers -- pointless because that's not what makes you decide to   
   use TCP or UDP.)   
      
   /Jorgen   
      
   --   
     // Jorgen Grahn    O  o   .   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)