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

RE: Update of a version-controlled collection with a checked-out member

From: Clemm, Geoff <gclemm@rational.com>
Date: Sat, 23 Feb 2002 18:53:44 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B105E4DA75@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
The result of applying an UPDATE to 
If the UPDATE succeeds, the server must delete the
checked-out version-controlled member,
but a server could very reasonably fail the request, in which case it
should return a DAV:update-version-controlled-collection-members element
in the DAV:error element.  Note that it could return additional information
to identify the checked-out resources that blocked the UPDATE, but we have
not defined any interoperable mechanism for doing so.


-----Original Message-----
From: Alison Macmillan [mailto:alison.macmillan@oracle.com]
Sent: Thursday, February 21, 2002 11:39 AM
To: ietf-dav-versioning@w3.org
Subject: Update of a version-controlled collection with a checked-out

What should happen if an UPDATE request is made for a version-controlled
collection which has a version-controlled internal member that is a
checked-out resource, and the DAV:version in the UPDATE request does not
identify the checked-out resource version-history in it's
DAV:version-controlled-binding-set? Should the UPDATE request fail, or
should the checked-out resource be deleted (by post condition

Similarly, what should happen if the checked-out resource is a member
(but not an internal member) of the collection,  and the UPDATE request
attempts to remove the collection resource that it is an internal member

 The statements and opinions expressed here are my own
 and do not necessarily represent those of Oracle Corporation.
Received on Saturday, 23 February 2002 18:54:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:48 UTC