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

No-checkout MERGE and version-controlled configurations

From: Roy Seto <Roy.Seto@oracle.com>
Date: Wed, 27 Feb 2002 15:20:18 -0800
To: "Ietf-Dav-Versioning@W3. Org" <ietf-dav-versioning@w3.org>
Message-ID: <MKEMLEPODEFMABCLLAOCAEPECBAA.Roy.Seto@oracle.com>
Consider a MERGE request whose request-URL has baseline-
controlled members, and which includes a DAV:no-checkout
element in the request body. Also, the DAV:auto-version
property value for the baseline-controlled members' 
version-controlled configuration is DAV:checkout.

Suppose the MERGE would cause an UPDATE to be applied to 
some of the members of the request-URL by MERGE 
postcondition DAV:descendant-version. Baseline 
autoversioning would cause the corresponding version-
controlled configuration to be checked out by the first
such UPDATE. Would this CHECKOUT attempt cause the MERGE
request to fail due to the DAV:no-checkout request-body
element?

I'd like clarification because I'm not sure whether the 
version-controlled configuration qualifies as a "merge
target" in this situation. From the 11.2 preconditions:

       (DAV:checkout-not-allowed): If DAV:no-checkout 
       is specified in the request body, it MUST be 
       possible to perform the merge without checking 
       out any of the merge targets.

Thanks,
Roy
Received on Wednesday, 27 February 2002 18:19:54 GMT

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