W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

12, 14.43: resource arguments and conneg

From: Paul Burchard <burchard@cs.princeton.edu>
Date: Sat, 01 Jun 1996 07:12:53 -0400
Message-Id: <31B025B5.41C6@cs.princeton.edu>
To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
Cc: fielding@ics.uci.edu
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/692
Roy's rewrite of the conneg sections in draft-04 is superb!  Just 
a small terminology nitpick:

Roy T. Fielding <fielding@ics.uci.edu> writes (14.43):
> An HTTP/1.1 server MUST include an appropriate Vary header field with
> any response that is subject to server-driven negotiation.
> A Vary field value consisting of a list of field-names signals that
> the representation selected for the response is based on a selection
> algorithm which considers ONLY the listed request-header field values
> in selecting the most appropriate representation.

Somehow the terminology needs to acknowledge that the responses
to methods which allow an entity-body in the request are already
assumed to depend on that entity-body -- but that this variation
is neither considered to be "content negotiation", nor a change
in the "requested resource".  Otherwise, the above could be
misconstrued to mean that POST automatically requires "Vary: *".

I think the simplest way is to talk about "resources (method calls)
with arguments".  If that concept is defined up front, the only
change needed within the conneg sections is to replace "resource"
by "resource with arguments" in most places.

Paul Burchard   <burchard@cs.princeton.edu>
``I'm still learning how to count backwards from infinity...''
Received on Saturday, 1 June 1996 04:17:15 UTC

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