From: grahn+nntp@snipabacken.se   
      
   On Thu, 12 Mar 2009 18:01:04 +0000 (UTC), Rick Jones    
   wrote:   
   > anil_ec1 <401anil@gmail.com> wrote:   
   >> Just githrough the manuals of TCP you can find more details. HTTP is   
   >> application layer protocol, and if it wants to communicate with any   
   >> other webser, there should be one connection. So TCP establishes   
   >> connection with the port number of 80(http).   
   >   
   > So, the _application_ implementing the HTTP protocol asks TCP to   
   > establish a connection between the local TCP endpoint and the remote   
   > TCP endpoint on the HTTP server waiting for connections on port 80.   
      
   Pedantic mode:   
   the application analyzes the HTTP URL to see if it requests some other   
   port. It also looks at its own configuration; if a HTTP proxy is   
   enabled, it uses that one instead.   
      
   And then we can talk hostname resolution, and the HTTP 1.1 case where   
   the application already *has* one or more TCP connections to the right   
   host ...   
      
   (My point is, I guess, it's probably better not to bring in HTTP if we   
   just want to talk about TCP ports.)   
      
   /Jorgen   
      
   --   
     // Jorgen Grahn           R'lyeh wgah'nagl fhtagn!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)