W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1996

Re: POST vs. separate methods

From: Larry Masinter <masinter@parc.xerox.com>
Date: Mon, 28 Oct 1996 17:13:06 PST
To: ejw@kleber.ics.uci.edu
CC: w3c-dist-auth@w3.org
Message-Id: <96Oct28.181306pdt."415911"@mule.parc.xerox.com>
> I'm interested in receiving feedback from the group on whether they feel
> having distributed authoring and versioning functionality is best
> performed via a POST (with many new content types), which is descreibed
> in the current spec., or whether it would be better to have this functionality
> implemented as many new methods, with parameters in headers, and mostly blank
> entity types.

The primary constraint, I think, is how various proxy & security
gateway services might deal with POST-with-new-entity-body vs. a new
method. A survey ("what's actually implemented?") would be useful,
since otherwise we're left with speculation.

A secondary issue (which doesn't actually affect the choice) is the
question of cache invalidation, e.g., after copy(a, b), any cache
entries for B should be invalidated even if are otherwise fresh, if
we're going to require sequential transparency of information
delivered through the same set of proxies.

E.g., if you do copy(a, b) and then ask for b, then YOU see the
version you copied even if others who use a different cache might be
updated later.

This is already an issue for POST, PUT and DELETE, but http-wg didn't
(yet) create any mechanism for doing this.


Received on Monday, 28 October 1996 21:13:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:09 UTC