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

Re: are depth 0 locks inherited by newly created children?

From: Greg Stein <gstein@lyra.org>
Date: Fri, 26 Nov 1999 11:12:38 -0800 (PST)
To: Jim Davis <jrd3@alum.mit.edu>
cc: w3c-dist-auth@w3.org
Message-ID: <Pine.LNX.4.10.9911261108250.18236-100000@nebula.lyra.org>
On Fri, 26 Nov 1999, Jim Davis wrote:
>...
> I read 7.5 as saying that even a depth zero lock is inherited, because it
> does not say "only depth infinity". You and others have asserted that this
> is bad.  When I asked why, you said it causes problems for BIND.

That's being a bit pedantic, don't you think? All right, so the RFC is
missing three words. Put them in and interpret it that way.

We know what the state of a Depth:0 lock on a collection is after one has
been applied (just the collection is locked), and we know the state after
a Depth:infinity has been applied (a bunch of stuff is locked). Your
"interpretation" would create situations that just don't match normal
behavior. With the simple insertion of three words, you get behavior that
matches for the PUT/MKCOL case and the LOCK case.

What I don't understand is how you could arrive at a reasonable
interpretation that the lock *should* be inherited. Could you explain?

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Friday, 26 November 1999 14:12:45 GMT

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