W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1995

Re: keep alive

From: John Franks <john@math.nwu.edu>
Date: Tue, 10 Oct 1995 11:17:45 -0500 (CDT)
Message-Id: <199510101617.LAA23042@hopf.math.nwu.edu>
To: Beth Frank <efrank@ncsa.uiuc.edu>
Cc: Anselm.Baird_Smith@inria.fr, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
According to Beth Frank:
> > 
> > I am looking for the precise spec of the keep-alive stuff. Mosaic
> > 2.7b1 and Netscape 2.0 (beta) both seems to follow this spec that I
> > haven't been able to locate. The only thing I am sure of, is that they
> > do not use the "draft-ietf-http-ses-ext-00.txt" adertized at
> > http://www.ics.uci.edu/pub/ietf/http/ (well, at least header names &
> > values differ).
> > 
> > Thanks for any pointers,
> > 
> > Anselm.
> > 
> > BTW: Is this is not the correct group for this kind of questions, let
> > me know.
> > 
> > Anselm.BairdSmith@inria.fr - http://www.inria.fr/koala/abaird.html
> Our documentation for keep-alive is at 
> 	http://hoohoo.ncsa.uiuc.edu/beta-1.5/howto/KeepAlive.html
> It references the spec mentioned above.  NCSA's implementation of the
> feature was completed shortly before that spec was released (and
> our beta was release that same week).  Our implementation was based
> on an earlier version of the spec, which I can't find now.  I believe
> Stan did a read-through of the new specification and found our
> implementation to be valid but missing some of the optional headers.
> 	-Beth
> PS. The Spyglass implementation does interoperate with NCSA's and
> 	I believe (but haven't confirmed) that Netscape's does as well.

The NCSA reference you give says:

   "Shortly after implementing the keepalive feature in HTTPd, a similar
   mechanism known as session extension, was proposed by the IETF for
   HTTP1.1. The mechanics are similar to our current implementation, but
   there are differences. We will most likely be modifying our keepalive
   implementation to be compatible with the session extension proposal
   during this beta. This should, for the most part, be transparent to
   the administration of HTTPd."

This together with the comment of Anselm above makes it sound as if your
implementation is not compatible with that spec. Is there any way that
browser or server writers can be compatible with you?  Is there any
description anywhere of what you have implemented?  If you interoperate
with Spyglass and Netscape how was this achieved without any specification?

John Franks
Received on Tuesday, 10 October 1995 09:27:17 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:15 UTC