W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1999

Re: Write Locks on Collections

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Tue, 23 Nov 1999 16:19:42 -0500
Message-Id: <9911232119.AA08625@tantalum>
To: w3c-dist-auth@w3.org

   From: Kevin Wiggen <wiggs@xythos.com>

   Jim Davis and I are having a discussion on what the appropriate behavior of
   a write lock on a collection should be.

   Re 7.5

   A write lock on a collection, whether created by a "Depth: 0" or "Depth:
   infinity" lock request, prevents the addition or removal of member URIs of
   the collection by non-lock owners.

I believe it says "internal member".

   If a lock owner causes the URI of a resource to be added as an internal
   member URI of a locked collection then the new resource MUST be
   automatically added to the lock.

I believe this statement should only apply to non-Depth:0 locks.
Otherwise, this results in the inability to independently lock
a collection and members of the collection.  This should be clarified/fixed
in the next draft of 2518.

   What does this mean when a collection is locked via a Depth 0 lock:

   1)  When a new resource is added to the collection, the resource is added
   without a lock as the parent has only a Depth 0 lock.

That's what I believe it should mean.

   2)  When a new resource is added to the collection, the resource is added
   and inherits the lock from above (via the second paragraph above)

That would be a very bad thing, if the collection lock is depth:0.

Received on Tuesday, 23 November 1999 16:19:49 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:20 UTC