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

Re: Write Locks on Collections

From: Greg Stein <gstein@lyra.org>
Date: Wed, 24 Nov 1999 00:58:57 -0800 (PST)
To: Jim Davis <jrd3@alum.mit.edu>
cc: w3c-dist-auth@w3.org
Message-ID: <Pine.LNX.4.10.9911240055450.10639-100000@nebula.lyra.org>
On Wed, 24 Nov 1999, Jim Davis wrote:
> A followup question for clarification 
> 
> Suppose I have a collection locked (at depth infinity), and I LOCK a  null
> resource (7.4) within it.
> 
> Does this action constitute adding a resource  "as an internal member URI
> of a locked collection " as in 7.5?
> 
> If so, then the locked-null resource now has two locks on it, right?

Yup. That's what mod_dav does.

Note that both locks must be shared.

And here is something that is really whacky: now remove the new lock --
the lock-null resource should still stick around since it had inherited
the lock from its parent collection. It will remain until that parent
collection's lock has been removed.

Fun, eh? :-)

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Wednesday, 24 November 1999 03:59:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:52 GMT