Re: COPY collection to an existing resource

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).

Cheers,
Geof

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.