W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2002

UPDATE responses for versioned collections

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 1 Oct 2002 15:05:13 +0200
To: <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCIEHJFHAA.julian.reschke@gmx.de>

Hi,

the spec says about the UPDATE method [1]:

"The response to an UPDATE request identifies the resources modified by the
request, so that a client can efficiently update any cached state it is
maintaining. Extensions to the UPDATE method allow multiple resources to be
modified from a single UPDATE request (see Section 12.13). "

When a versioned collection is updated, this may affect the versioned
collections and all it's internal members. One possible state transition is
that a child is removed.

For instance, let "/a" be a versioned collection with a version controlled
member "/a/b". I update "/a" from a collection version which doesn't have
"b" in it's version-controlled-binding-set. "/a/b" gets removed. What
response do we expect?

 <D:multistatus xmlns:D="DAV:">
  <D:response>
    <D:href>/a/</D:href>
    <D:status>HTTP/1.1 200 OK</D:status>
  </D:response>
  <D:response>
    <D:href>/a/b</D:href>
    <D:status>HTTP/1.1 404 Not Found</D:status>
  </D:response>
</D:multistatus>

or

 <D:multistatus xmlns:D="DAV:">
  <D:response>
    <D:href>/a/</D:href>
    <D:status>HTTP/1.1 200 OK</D:status>
  </D:response>
</D:multistatus>

?


[1] <http://greenbytes.de/tech/webdav/rfc3253.html#METHOD_UPDATE>

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 1 October 2002 09:05:45 GMT

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