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

Re: proppatch label-name-set?

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Tue, 16 Jan 2001 12:49:01 -0500 (EST)
Message-Id: <200101161749.MAA17454@tantalum.atria.com>
To: ietf-dav-versioning@w3.org

   From: Greg Stein <gstein@lyra.org>

   Is it legal to PROPPATCH the DAV:label-name-set on a checked-out resource?
   (whether a checked-out VCR or a working resource)

Only versions have a DAV:label-name-set property, not
version-controlled resources or working resources.

   It seems feasible to me, with the caveat of possible rejection at CHECKIN
   (or MERGE) time due to a label conflict with another version in the version

The possibility of a "label conflict" is avoided by only having
labels on versions.

   Specifically, the problem that I'm considering is how to label a baseline
   before checking it in. I think that I'm also okay with labelling via a
   second request (after the checkin/merge), but that does lead to a race
   between the checkin and label that I'd like to avoid if possible.

With the current protocol, you would have to do the labeling in a
second request (after the version was created).  What is the race
condition you were concerned about?  And how would it be addressed
by allowing a label on a working baseline?

Received on Tuesday, 16 January 2001 12:49:53 UTC

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