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

Re: rfc2518 issue: DEFER_LOCK_NULL_RESOURCES_IN_SPEC

From: Ilya Kirnos <ilya.kirnos@oracle.com>
Date: Thu, 09 Aug 2001 00:15:09 -0700
Message-ID: <3B72387D.29EABA74@oracle.com>
To: w3c-dist-auth@w3.org
(apologies if this is a duplicate)


Stefan Eissing wrote:
> 
> > [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Clemm, Geoff
> > Sent: Monday, August 06, 2001 1:13 AM
> > To: w3c-dist-auth@w3.org
> > Subject: RE: rfc2518 issue: DEFER_LOCK_NULL_RESOURCES_IN_SPEC
> >
> >
> > The full proposal I advocate is as follows:
> >
> > Delete all references to the term "lock null resource".
> >
> > Instead, in the LOCK semantics, add the following:
> >
> > "If a LOCK request is applied to an unmapped URL, the server
> > MUST automatically precede the LOCK request with the creation
> > of a resource at the request URL.
> > This automatically created resource has the same behavior as
> > a resource created by a PUT with a zero length body.
> > In particular, it is never automatically deleted when it is
> > UNLOCK'ed.  Note that this changes the behavior defined in
> > RFC-2518, which stated that the resource MUST be automatically
> > deleted if it is unlocked before it has been explicitly updated
> > (e.g. by a PUT)."
> >
> > I believe that this reference to the old 2518 semantics is sufficient.
> 
> I fully agree and support the proposal.
> 
> //Stefan


This sounds good to me as well.

-ilya
Received on Thursday, 9 August 2001 03:14:36 GMT

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