Re: HTTP was OS/400 command set

["Adam Lang" <aalang@xxxxxxxxxxxxxxxxxxxx>]

http://www.w3.org/Protocols/HTTP/1.1/rfc2616.pdf

Section 8.1

Since HTTP1.1 there are ways to imlpement persistent connections, but they
emphasize "should" support.  A persistent connection can not be guaranteed.

Here is a sort of interesting page from Apache.

http://httpd.apache.org/docs/keepalive.html

So in essence, Scott and I are both correct. :)

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:54 AM
Subject: Re: HTTP was OS/400 command set


> From: Adam Lang <aalang@rutgersinsurance.com>
> > It doesn't know.
> > You request one resource at a time.  After you get that resource,
> connection
> > closes.
> > > 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.
> > >
>
> you fight this out with Scott   :-)
> AFAICT, your two postings are contradictory....
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.