- From: Tim Ellison <tim@peir.com>
- Date: Fri, 15 Jun 2001 21:03:52 +0100
- To: <w3c-dist-auth@w3.org>
This is cool. > A lock-null resource is a null resource that has been locked. A lock null > resource has diferent properties that a null resource. Specifically, it has > at least the lock discovery properties, and it is a member of its parent's > collection. Now I'm confused again. A lock-null resource (i.e. a URI that has no resource binding) is-a locked resource? How did you make that leap? Is it fair to think of LOCK on a (unmapped) URI as creating a resource just as I think of PUT creating a resource? If not, why? > > If a lock null resource is not a resource, then what is it? > > Since a lock null resource has state, I would claim it is a resource. By the > act of a client taking out a lock, they have likely made a mapping of a URL > to a conceptual resource, and are int he process of fleshing out the > computer representation of the conceptual resource. Agreed. Tim
Received on Friday, 15 June 2001 16:03:54 UTC