W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1997

Re: Locks, reservations, copies and moves

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>
Message-ID: <Pine.SGI.3.95.970828100805.2901B-100000@twaxx.twaxx.com>
> 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.

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

Received on Thursday, 28 August 1997 13:13:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:11 UTC