- From: -=jack=- <jack@twaxx.twaxx.com>
- Date: Thu, 28 Aug 1997 10:12:07 -0700 (PDT)
- To: Dylan Barrell <dbarrell@opentext.ch>
- cc: "'WebDAV'" <w3c-dist-auth@w3.org>
> The simplest solution seems to me to do the following > > 1. Disallow moving of locked or reserved resources (or at least resource locked as part of a multi.-resource lock) ------------------- [my opinion!]: destructive operations on the *original* resource should be disallowed. destructive op's on a *copy* of the orig resource should be allowed, unless the copy is subsequently locked... > 2. Specifically state that the correct behaviour in the case of a COPY is to NOT copy the locks or reservations. ------------ agreed. > 3. Change the definition of MOVE to be independent of COPY ----------------- definition should be independant, but implementation *could* be performed as described or otherwise, as long as it's transparent to the user... just my $0.02... -=j=-
Received on Thursday, 28 August 1997 13:13:57 UTC