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

RE: what is lock-null resource

From: <Tim_Ellison@uk.ibm.com>
Date: Fri, 15 Jun 2001 11:04:33 +0100
To: "WebDAV WG" <w3c-dist-auth@w3.org>
Message-ID: <80256A6C.0037470F.00@d06mta06.portsmouth.uk.ibm.com>


"Dr. Michael Evans" <mike.evans@glowebs.com> wrote:
> A null resource is defined as a resource which responds
> with a 404 (Not Found) to any HTTP/1.1 or DAV method except
> for PUT, MKCOL, OPTIONS and LOCK



and UNLOCK.

> In other words, a null resource is one that does not physically
> exist on the server, but whose URL does.

I can't let that sentence go <g>.

The protocol does not state which resources physically exist and which do
not, that is the perogative of the server implementation.  Given that the
lock null resource has all the mandatory DAV properties I would imagine
that many server implementations _would_ have to 'physically' persist a
lock null resource.

As for the URL physically existing, "As far as HTTP is concerned, Uniform
Resource Identifiers are simply formatted strings which identify--via name,
location, or any other characteristic--a resource." [RFC2616]

> Locking a null resource has the effect of reserving the URL.
> In this way, a write-locked null resource (or lock-null
> resource) ensures that no other user can use the specified
> URL until it is unlocked.

Tim
Received on Friday, 15 June 2001 06:05:43 GMT

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