Re: 1.1b3 and things???

  "for a while yet". I might point out that, for example, one out of   every thirty servers still runs NCSA httpd 1.3, a server that's   severely out of date, not to mention the security holes. Counting on   people to upgrade servers is never a good idea.

But that's not what I'm counting on. I'm counting on them not to *write* any *clients* that speak HTTP/1.1 to the exclusion of HTTP/1.0 Keep-alive syntax. So long as the clients are willing to speak HTTP/1.0 to HTTP/1.0 servers, everything works.

In fact, the reason I'm counting on this is the very fact you state --- that HTTP/1.0 servers will still be around for while yet, and HTTP/1.1 clients are going to have to be written to deal with them, including their idiosyncratic keep-alive syntax.

To put it another way --- you're assuming an HTTP/1.1 client which simply does not understand HTTP/1.0 keepalives. They don't exist now. (No HTTP/1.1 clients exist now). Why would anybody write one?

rst Received on Sun Jun 9 12:16:10 1996