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

RE: No-checkout MERGE and version-controlled configurations

From: Clemm, Geoff <gclemm@rational.com>
Date: Sat, 2 Mar 2002 08:25:36 -0500
Message-ID: <3906C56A7BD1F54593344C05BD1374B105F84D80@SUS-MA1IT01>
To: "Ietf-Dav-Versioning@W3. Org" <ietf-dav-versioning@w3.org>
I would not call the auto-versioned VCCn a merge target,
therefore I would not consider this auto-checkout as a
violation of the DAV:checkout-not-allowed precondition.


-----Original Message-----
From: Roy Seto [mailto:Roy.Seto@oracle.com]
Sent: Wednesday, February 27, 2002 6:20 PM
To: Ietf-Dav-Versioning@W3. Org
Subject: No-checkout MERGE and version-controlled configurations

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

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.

Received on Saturday, 2 March 2002 08:26:09 UTC

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