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

Re: Creating a lock-null in a locked collection

From: Joe Orton <joe@orton.demon.co.uk>
Date: Fri, 31 Dec 1999 00:37:59 +0000
To: "Yaron Goland (Exchange)" <yarong@Exchange.Microsoft.com>
Cc: w3c-dist-auth@w3.org
Message-ID: <19991231003759.B4902@ankh.dunno.local>
> The depth 0 lock controls the ability to add level 1 children to the
> collection.
> A lock null resource is a resource and hence is a member of whatever
> collections it exists within.
> Therefore to create a lock null resource as a level 1 child of a collection
> with a depth 0 lock one must have the depth 0 lock.
> In other words, yes, you must submit the token on the LOCK on /foo/bar.

Okay, thanks. It just seemed slightly weird, that if you LOCK or UNLOCK a
lock-null resource, you are modifying the state of the parent collection;
when if you do the same to a normal resource, you are not.


Received on Thursday, 30 December 1999 19:48:30 UTC

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