W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2003

RE: BIND and DAV:checkout-set property

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Mon, 1 Sep 2003 22:28:13 -0400
To: ietf-dav-versioning@w3.org
Message-ID: <OFE51F0414.519A7D47-ON85256D95.00064E70-85256D95.000D91C1@us.ibm.com>
"Nevermann, Dr., Peter" <Peter.Nevermann@softwareag.com> wrote on 
09/01/2003 07:00:39 AM:

> > (I suggest to) store the URI that the CHECKOUT 
> > request was applied to.  This is likely to be the 
> > behavior that is most expected by clients that are 
> > not written with multiple bindings in mind.
> What happens, if the URI that the CHECKOUT request was applied to 
> becomes unvalid - e.g. because of UNBIND somewhere above in the 
> hierarchy.

By the definition of the DAV:checkout-set property, in case of an
REBIND/MOVE or a UNBIND/DELETE, the server would
have to update the DAV:checkout-set to ensure that it correctly
identifies (i.e. has valid URLs for) the current set of checked-out

> If I still have a path to the resource, should UNCHECKOUT
> or CHECKIN still work with the alternate path?


Received on Monday, 1 September 2003 22:28:29 UTC

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