W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2001

Re: Autoversion confusion

From: Greg Stein <gstein@lyra.org>
Date: Fri, 9 Feb 2001 04:45:13 -0800
To: ietf-dav-versioning@w3.org
Message-ID: <20010209044513.U26044@lyra.org>
On Fri, Feb 09, 2001 at 09:58:29AM +0000, Tim_Ellison@uk.ibm.com wrote:
> John wrote:
> > This shouldn't be necessary, since the HTTP spec
> > defines the behavior of GET and PUT. Specifically,
> > it says that PUT to a particular resource defines
> > the response for any following GET on that same
> > resource (I'm paraphrasing from memory). There
> > can't be any other possible interpretation (that
> > doesn't break HTTP semantics).
> 
> I agree with John.
> 
> At the risk of nagging<g>, a version-controlled resource is an honest to
> goodness WebDAV resource, with content and properties (version-controlled
> collections have members and properties).  Intuatively, if a PUT to the
> resource succeeds (200 OK) then a client is entitled to believe they will
> GET the same entity back.
> 
> p.s.
> I had a quick look through the HTTP/1.1 spec, and didn't see anything that
> states this categorically.  In fact, Section 9.6 (PUT) states:
>  "HTTP/1.1 does not define how a PUT method affects the state of an origin
> server."
> Now, how many clients do a GET just to check what they actually will
> retrieve after a successful PUT!

Section 8.7.1 of RFC 2518 has what you're looking for :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Friday, 9 February 2001 07:43:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:40 GMT