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

Re: new proposed text for locking overview

From: Jason Crawford <ccjason@us.ibm.com>
Date: Tue, 6 Jul 2004 15:28:20 -0400
To: Julian Reschke <nnjulian.reschke___at___gmx.de@smallcue.com>
Cc: WebDAV <nnw3c-dist-auth___at___w3.org@smallcue.com>
Message-ID: <OF9599C94D.FFCF6C3E-ON85256EC9.0069744B-85256EC9.006AF8E9@us.ibm.com>
On Tuesday, 07/06/2004 at 08:10 ZE2, Julian Reschke wrote:


> 2.5  Status of a lock
> 
> Having a URI (the lock token URI) on it's own, a lock is a resource
> in the sense defined by [RFC2396].  In general, this resource does
> not have a HTTP URL, and thus can not be directly manipulated using
> HTTP methods.  Instead, this specification defines the new methods
> LOCK (creating and refreshing locks, see Section 4) and UNLOCK
> (removing locks, see Section 5) that act indirectly on locks.

I don't like us calling a lock a resource. 


The other paragraphs you included seem reasonable.
Received on Tuesday, 6 July 2004 15:28:40 GMT

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