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

Re: COPY collection to an existing resource

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Thu, 13 Jul 2006 08:44:24 -0400
To: werner.donne@re.be
Cc: ietf-dav-versioning@w3.org, ietf-dav-versioning-request@w3.org
Message-ID: <OF0CD84BC5.F8B200EE-ON852571AA.0045D4A1-852571AA.0045FB96@us.ibm.com>
Yes, and note that a client can also just DELETE the target before 
requesting the COPY, in which case a fresh set of resources would be 
created at the destination (each with a new version history, if the server 
automatically puts new resources under version control).


Werner wrote on 07/13/2006 05:53:37 AM:

> In other words, the position is taken that when a user
> copies a collection to an existing destination, both are
> likely to be related to the user. Otherwise strange
> version histories would result for internal members that
> happen to coincide. This position seems reasonable.
> There is a practical consequence for the user, however.
> Since the operation is recursive, the user has to be aware
> of the internal members that coincide at any depth and
> make sure that either they are checked out or that their
> "auto-version" property is set properly. It is also
> necessary that all subcollections at the destination are
> checked out or have the appropriate auto-version property.
Received on Thursday, 13 July 2006 12:44:38 UTC

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