Mailing-List: contact new-httpd-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: new-httpd@apache.org
Message-ID: <044201c0c8cd$3062b500$e4421b09@raleigh.ibm.com>
From: "Bill Stoddard" <bill@wstoddard.com>
To: <new-httpd@apache.org>
References: <20010418035335.75717.qmail@apache.org>
 <20010419011350.B2501@borg.ebuilt.net> <3ADEC763.C78F2695@covalent.net>
Subject: Re: cvs commit: httpd-2.0/server protocol.c
Date: Thu, 19 Apr 2001 08:35:17 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


> Roy,
>
> fielding@ebuilt.com wrote:
> >
> > >   Move the keepalives field out of the conn_rec and into an HTTP specific
> > >   connection record.  This also moves some HTTP specific back out of the
> > >   core and into the HTTP module.
> >
> > -1.  First, as I said at the hackathon, these variables are not specific
> > to HTTP.  They record and control limitations on the number of requests
> > per connection.  You can change their names, if you want, but they must
> > be in the connection record for all protocols.
>
> OK, I was not at the HACKATON, but 'keepalive' is an HTTP
> specific protocol mechanism. If not, please refer me to some
> protocol that uses it?? :-))
>

The protocol Lotus Notes uses is keepalive (yea, it is a proprietary protocol and may not count in
this discussion).  Doesn't BXXP (is that what it is called now?) maintain persistent connections?  I
know of more obscure proprietary protocols that flow multiple requests/response pairs over a
persistent connection.

Bill