W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2006

Re: Precondition add-must-be-new-label

From: Werner Donné <werner.donne@re.be>
Date: Sun, 16 Jul 2006 10:38:12 +0200
Message-ID: <44B9FAF4.9070803@re.be>
To: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Cc: ietf-dav-versioning@w3.org

Thank you Geoff. I wrongly interpreted the "set" operation as
replacing the label-name-set of a version with a singleton
containing the provided new label name.

Regards,

Werner.

Geoffrey M Clemm wrote:
> 
> The add-must-be-new precondition only applies if DAV:add is specified in
> the LABEL request (i.e. you want it to fail if the label is already
> applied to some version).
> 
> You use DAV:set in the LABEL request if you want to move the label from
> one version to another.
> 
> Cheers,
> Geoff
> 
> Werner wrote on 07/14/2006 12:58:41 PM:
> 
>>
>> Hi,
>>
>> The add-must-be-new precondition of the LABEL method makes it
>> impossible to move a label. Moving a label requires a remove
>> followed by an add, which are two round-trips. Instead of
>> having the precondition, the postcondition label-must-be-unique
>> would provide the same data integrity, while avoiding the
>> extra round-trip.
>>
>> An additional advantage is that the move would be atomic. A
>> remove followed by an add is not. The impact of a failure in
>> between can be dramatic.
>>
>> Regards,
>>
>> Werner.
>> --
>> Werner Donné  --  Re
>> Engelbeekstraat 8
>> B-3300 Tienen
>> tel: (+32) 486 425803   e-mail: werner.donne@re.be
>>

-- 
Werner Donné  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: werner.donne@re.be
Received on Sunday, 16 July 2006 08:37:26 GMT

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