Re: COPY collection to an existing resource

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.

Regards,

Werner.
--=20
Werner Donn=E9  --  Re
Engelbeekstraat 8
B-3300 Tienen
tel: (+32) 486 425803	e-mail: [email protected]