W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2000

UNLOCK from the middle of a locked tree

From: Slein, Judith A <JSlein@crt.xerox.com>
Date: Fri, 10 Mar 2000 16:03:22 -0500
Message-ID: <8E3CFBC709A8D21191A400805F15E0DB0211F99B@crte147.wc.eso.mc.xerox.com>
To: "'w3c-dist-auth@w3.org'" <w3c-dist-auth@w3.org>
Cc: "Hall, Shaun" <Shaun.Hall@GBR.XEROX.COM>
I have this question from a product team in my company.  Any opinions?  I
would say that (b) is not an option, but failing the unlock request might
be.

--Judy

Section 8.11 UNLOCK Method. The first sentence states "...and all other
resources included in the lock". Does this mean that a client should only
Unlock from the point where the lock starts? For example, in a hierarchy:

		Collection 1
		|	  |
	    Collection 2	Collection 3
		|	  |
	    Resource 4	Resource 5

If the lock was created with a Depth of infinity on "Collection 1", should
the user only perform the UNLOCK on "Collection 1"?

We're concerned that a client may try and unlock from a sub-point within the
hierarchy eg UNLOCK "Collection 2", which means to meet the first sentence
in the RFC, we either:

a) Have to traverse the entire hierarchy (parents and all) removing the lock
from all resources (in the above example, "Collection 1", "Collection 3" and
"File 5").

b) Only remove the lock from "Collection 2" and "File 4".
Received on Friday, 10 March 2000 16:03:26 GMT

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