Re: HTTP was OS/400 command set

It doesn't know.

You request one resource at a time.  After you get that resource, connection
closes.

For each resource a new connection is made.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Leif Svalgaard" <leif@leif.org>
To: <midrange-l@midrange.com>
Sent: Thursday, November 14, 2002 10:33 AM
Subject: Re: OS/400 command set


> From: Scott Klement <klemscot@klements.com>
> > No, HTTP is not "connectionless".   When you get something from a web
> > server, you connect, you request a document, it sends it, you request
> > the next, it sends it, etc... all during one TCP connection.
>
> The "etc" bothers me. How does it know when my current request is
> going to be the last? The only way this can happen is that the
> connection times out after a (long!) time, because I can sit there
> staring at a webpage for hours before requesting "the next all
> during one TCP connection". Something fishy here....