W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1997

Re: [Fwd: Re: PEP draft for review]

From: Koen Holtman <koen@win.tue.nl>
Date: Thu, 13 Feb 1997 20:51:47 +0100 (MET)
Message-Id: <199702131951.UAA02723@wsooti08.win.tue.nl>
To: Dan Connolly <connolly@w3.org>
Cc: koen@win.tue.nl, http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/2361
Dan Connolly:
>Koen Holtman wrote:
>> Dan Connolly:
>> >Protocol-Info, on the other hand, is an entity header: it applies
>> >to resources, either those explicitly named using the "for" syntax,
>> Doesn't protocol-info apply to a single hop in the connection, not to the
>> resource on the origin server, when {scope conn} is used?
>There isn't any 'hop-only protocol info.'

Thanks, I think I understand now.  I thought that {scope conn} marked pep
extensions which are negotiated by two parties spanning a single hop in the
connection, while it actually marks extentions which require the
participation of every party along the connection.


Received on Thursday, 13 February 1997 11:59:30 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:01 UTC