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

Re: Creating a lock-null in a locked collection

From: <jamsden@us.ibm.com>
Date: Thu, 30 Dec 1999 12:18:21 -0500
To: w3c-dist-auth@w3.org
Message-ID: <85256857.0082BD5E.00@d54mta03.raleigh.ibm.com>

You will need to include the lock token for /foo/ as you are adding a
member to this collection even though its a lock-null resource. If you do a
PROPFIND with depth:0 on /foo/, you'll see the lock-null resource even
before you do the initial PUT proving the collection's members, and
therefore it state, were modified.

Joe Orton <joe@orton.demon.co.uk>@w3.org on 12/30/99 09:45:10 AM

Sent by:  w3c-dist-auth-request@w3.org

To:   w3c-dist-auth@w3.org

Subject:  Creating a lock-null in a locked collection

I have an depth 0 write lock on /foo/. If I do LOCK /foo/bar to create a
lock-null resource, do I need to submit the locktoken for /foo/ in the
LOCK request? Or only in the PUT to /foo/bar later?

(Or is it decided that lock-null resources are going to go away?)

Received on Thursday, 30 December 1999 18:48:08 UTC

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