Re: Precondition add-must-be-new-label
Geoffrey M Clemm <[email protected]> Sat, 15 Jul 2006 11:47:42 -0400
| Newsgroups | gmane.ietf.deltav |
|---|---|
| Message-ID | <OFEE6F5F8F.1991B300-ON852571AC.00568509-852571AC.0056C399@us.ibm.com> |
This is a multipart message in MIME format. --=_alternative 0056C321852571AC_= Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable The add-must-be-new precondition only applies if DAV:add is specified in=20 the LABEL request (i.e. you want it to fail if the label is already=20 applied to some version). You use DAV:set in the LABEL request if you want to move the label from=20 one version to another. Cheers, Geoff Werner wrote on 07/14/2006 12:58:41 PM: >=20 > Hi, >=20 > 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. >=20 > 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. >=20 > Regards, >=20 > Werner. > --=20 > Werner Donn=E9 -- Re > Engelbeekstraat 8 > B-3300 Tienen > tel: (+32) 486 425803 e-mail: [email protected] >=20 --=_alternative 0056C321852571AC_= Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable <br><font size=3D2 face=3D"sans-serif">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).</font> <br> <br><font size=3D2 face=3D"sans-serif">You use DAV:set in the LABEL request if you want to move the label from one version to another.</font> <br><font size=3D2 face=3D"sans-serif"><br> Cheers,<br> Geoff</font> <br> <br><tt><font size=3D2>Werner wrote on 07/14/2006 12:58:41 PM:<br> <br> > <br> > Hi,<br> > <br> > The add-must-be-new precondition of the LABEL method makes it<br> > impossible to move a label. Moving a label requires a remove<br> > followed by an add, which are two round-trips. Instead of<br> > having the precondition, the postcondition label-must-be-unique<br> > would provide the same data integrity, while avoiding the<br> > extra round-trip.<br> > <br> > An additional advantage is that the move would be atomic. A<br> > remove followed by an add is not. The impact of a failure in<br> > between can be dramatic.<br> > <br> > Regards,<br> > <br> > Werner.<br> > -- <br> > Werner Donn=E9 -- Re<br> > Engelbeekstraat 8<br> > B-3300 Tienen<br> > tel: (+32) 486 425803 e-mail: [email protected]<br> > <br> </font></tt> --=_alternative 0056C321852571AC_=--