W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 1998

lock_null_prop

From: Yaron Goland <yarong@microsoft.com>
Date: Sun, 5 Apr 1998 18:30:14 -0700
Message-ID: <3FF8121C9B6DD111812100805F31FC0D02971187@red-msg-59.dns.microsoft.com>
To: "'WEBDAV WG'" <w3c-dist-auth@w3.org>
lock_null_prop	We need to clarify that lock-null resources must define all
mandatory properties

Another clarification is that a lock-null resource must return all the
mandatory DAV properties. The purpose is to make lock-null resources walk
and talk as closely as is reasonable to normal DAV resources, especially
because they appear in the collection namespace.

6.3	Write Locks and Null Resources

	It is possible to assert a write lock on a null resource in order to
lock the name.

	A write locked null resource, referred to as a lock-null resource,
MUST respond with a 404 Not Found or 405 Method Not Allowed to any HTTP/1.1
or DAV methods except for PUT, MKCOL, OPTIONS, PROPFIND, LOCK, and UNLOCK.
A lock-null resource MUST appear as a member of its parent collection.
Additionally the lock-null resource MUST have defined on it all mandatory
DAV properties.  Most of these properties, such as all the get* properties,
will have no value as a lock-null resource does not support the GET method.
Lock-Null resources MUST have defined values for lockdiscovery and
supportedlock properties.

	Until a method such as PUT or MKCOL is successfully executed on the
lock-null resource the resource MUST stay in the lock-null state.  However,
once a PUT or MKCOL is successfully executed on a lock-null resource the
resources ceases to be in the lock-null state.

	If the resource is unlocked, for any reason, without a PUT, MKCOL,
or similar method having been successfully executed upon it then the
resource MUST return to the null state.

			Yaron
Received on Sunday, 5 April 1998 21:30:17 GMT

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