Re: DAV:cannot-copy-collection-version precondition for COPY
Manfred Baedke <[email protected]> Tue, 22 Aug 2006 18:18:12 +0200
| Newsgroups | gmane.ietf.deltav |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. --------------080901010104080405080409 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Hi Werner, taking into account the postcondition=20 (DAV:must-not-copy-versioning-property) and the fact that the property=20 DAV:version-controlled-binding-set is more or less all a collection=20 version has to offer, there is nothing left to be copied. Regards, Manfred Werner Donn=E9 wrote: > A collection version has the names of its version controlled bindings > and their version history. It is then possible to find the checked-in > version of the members, which is what is used also when a collection > is copied. > > Regards, > > Werner. > > Geoffrey M Clemm wrote: > =20 >> A collection version does not have enough information in it to produce= a >> sensible copy, since it only records the version history of its member= s, >> not the versions. So a collection version is useful for updating a >> configuration, but is not useful for creating a new configuration >> (that's what baselines are for). >> >> Cheers, >> Geoff >> >> [email protected] wrote on 08/22/2006 06:34:16 AM: >> >> =20 >>> Hi, >>> >>> Why should the request fail if the source is a collection version? >>> It seems to me that any version is as good as the checked-in version >>> to copy from. >>> >>> Regards, >>> >>> Werner. >>> -- >>> Werner Donn=E9 -- Re >>> Engelbeekstraat 8 >>> B-3300 Tienen >>> tel: (+32) 486 425803 e-mail: [email protected] >>> >>> =20 > > =20 --------------080901010104080405080409 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type"> <title></title> </head> <body bgcolor="#ffffff" text="#000000"> Hi Werner,<br> <br> taking into account the postcondition (DAV:must-not-copy-versioning-property) and the fact that the property DAV:version-controlled-binding-set is more or less all a collection version has to offer, there is nothing left to be copied.<br> <br> Regards,<br> Manfred<br> <br> Werner Donné wrote: <blockquote cite="[email protected]" type="cite"> <pre wrap="">A collection version has the names of its version controlled bindings and their version history. It is then possible to find the checked-in version of the members, which is what is used also when a collection is copied. Regards, Werner. Geoffrey M Clemm wrote: </pre> <blockquote type="cite"> <pre wrap="">A collection version does not have enough information in it to produce a sensible copy, since it only records the version history of its members, not the versions. So a collection version is useful for updating a configuration, but is not useful for creating a new configuration (that's what baselines are for). Cheers, Geoff <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> wrote on 08/22/2006 06:34:16 AM: </pre> <blockquote type="cite"> <pre wrap="">Hi, Why should the request fail if the source is a collection version? It seems to me that any version is as good as the checked-in version to copy from. Regards, Werner. -- Werner Donné -- Re Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: <a class="moz-txt-link-abbreviated" href="mailto:[email protected]">[email protected]</a> </pre> </blockquote> </blockquote> <pre wrap=""><!----> </pre> </blockquote> </body> </html> --------------080901010104080405080409--