My experience so far, has been that, if you send a "Connection: Keep-Alive"
in the HTTP headers of the object the browser asked for, and not close the
connection, the browser will ask you for more objects (if there are any
more). It's as simple as that.
This works with both IE/Netscape.
Arun.
----- Original Message -----
From: "Wirta, Ville" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, September 20, 2000 7:14 AM
Subject: keep-alive
> Hi!
>
> I'm deeply sorry that I have to ask (again) something that isn't ment to
be
> asked on this list but I have no one else to turn to but You guys and
gals.
> (thank God and The OpenSSL Project Team for this list! I mean really...)
>
> The problem in a nutshell:
> I'd need to implement connection keep-alive to a thread based www-server.
> Does anyone know a good place in the web where to start digging? Or even
> better if anyone wants to light me up on this one. RFC 2616 (HTTP/1.1)
> was'nt for much help. I'd need to understand how things work between the
> browser and the server (not only be told how they SHOULD work --> RFC),
what
> the server should send the browser to make it send more requests while the
> socket is still open etc. (Now IE waits something till the end of the
world
> and does'nt ask for the next item on the page.)
>
> I'll be grateful for even a slight advice but the biggest hand in need is
a
> hand indeed!
>
> Yours cincerelly VW
>
> ______________________________________________________________________
> OpenSSL Project http://www.openssl.org
> User Support Mailing List [EMAIL PROTECTED]
> Automated List Manager [EMAIL PROTECTED]
>
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
