- From: Stefan Eissing <stefan.eissing@greenbytes.de>
- Date: Fri, 27 Sep 2002 10:48:02 +0200
- To: "Clemm, Geoff" <gclemm@rational.com>
- Cc: ietf-dav-versioning@w3.org
While we're at this topic: we have a similar issue with auto-update of version controlled collections. - checkout a versioned collection with apply-to-version - remove a member from the working collection - checkout in-place the member of the versioned controlled collection - checkin the working collection -> the version controlled collection should be updated an remove the binding to the checked-out resource. I think the checkin should fail in this case, as the removal of a checked-out member might cannot be permitted. Do you agree? //Stefan Am Donnerstag, 26.09.02, um 20:33 Uhr (Europe/Berlin) schrieb Clemm, Geoff: > From: Julian Reschke [mailto:julian.reschke@greenbytes.de] > > section 7.1 defines the UPDATE semantics checked-in resources: > > "The UPDATE method modifies the content and dead properties of a > checked-in version-controlled resource (the "update target") to be > those of a specified version (the "update source") from the version > history of that version-controlled resource." > > So is the behaviour for checked-out resources just undefined > (intentionally)? > > I would have expected that DAV:must-be-checked-in is an explicit > precondition for this method... > > I agree that adding the DAV:must-be-checked-in precondition is the > better answer. I'll add this to the Errata, and resolve it by adding > that precondition, unless someone objects. > > Cheers, > Geoff >
Received on Friday, 27 September 2002 04:48:33 UTC