W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2002

RE: discovering the root of a deep lock

From: Clemm, Geoff <gclemm@rational.com>
Date: Wed, 10 Jul 2002 09:22:04 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B107761316@SUS-MA1IT01>
To: w3c-dist-auth@w3.org

I agree that the lock discovery should report on
the root of a depth lock.

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Wednesday, July 10, 2002 3:39 AM
To: w3c-dist-auth@w3.org
Subject: discovering the root of a deep lock



(see also issue LOCKS_SHOULD_THEY_USE_AN_IF_HEADER_TO_VERIFY)

Proposed syntax:

12.1  activelock XML Element

Name:
activelock
Namespace:
DAV:
Purpose:
Describes a lock on a resource.

   <!ELEMENT activelock (lockscope, locktype, depth, owner?, timeout?,
locktoken?, lockroot?) >


12.1.x  lockroot XML Element

Name:
lockroot
Namespace:
DAV:
Purpose:
For locks with depth infinity, servers SHOULD report the root of the lock
using the DAV:lockroot element. This enables clients to know the scope of
resources affected by a subsequent UNLOCK with the given lock token. For
lock with depth 0, the DAV:lockroot element MUST NOT be present.

   <!ELEMENT lockroot (href) >


--

Note: I made it a "SHOULD" in order not to break existing implementations.
Received on Wednesday, 10 July 2002 09:22:36 GMT

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