- From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
- Date: Mon, 1 Sep 2003 22:28:13 -0400
- To: ietf-dav-versioning@w3.org
Received on Monday, 1 September 2003 22:28:29 UTC
"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 resources. > If I still have a path to the resource, should UNCHECKOUT > or CHECKIN still work with the alternate path? Yes. Cheers, Geoff
Received on Monday, 1 September 2003 22:28:29 UTC