🚀 go-pugleaf

Thank you Hans and Remy for responding, I appreciate it very much.

So my understanding of your response is that the data positioned after the 
port identity is just sent to the application listening on the port. It 
would be the same as if an application using sockets to talk to a module 
running on the server sent data on the socket port.

Am I correct on this interpretation.

Mike

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:440801d4@newsgroups.borland.com...
>
> "mike" <mfbrowne@earthlink.nnet> wrote in message
> news:4407c261$1@newsgroups.borland.com...
>
>> I have a basic question that I am trying to understand.
>
> Have a look at RFC 1945 (http://www.ietf.org/rfc/rfc1945.txt) and RFC 2616
> (http://www.ietf.org/rfc/rfc2616.txt).  They describe the semantics of the
> HTTP protocol at the TCP/IP level.
>
> As for what happens on the server, when it receives the request you
> showedrequest, it parses the string "/help/12345/full", decides what to do
> with it, and then returns the appropriate data back to the browser.  The
> string is just a string, so the server can process it any way it wishes. 
> It
> does not have to be a physical file or folder.  All the server has to do 
> is
> receive requests and send responses.  How it decides what data to send is 
> at
> the server's descretion.
>
>
> Gambit
>
>