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

RE: Status code for creating lock-null resource

From: Hall, Shaun <Shaun.Hall@gbr.xerox.com>
Date: Thu, 21 Jun 2001 09:20:21 +0100
Message-ID: <59697CCC6CE3D411B4CD00805FBB77672875C8@gbrwgcms03.wgc.gbr.xerox.com>
To: WebDAV WG <w3c-dist-auth@w3.org>
> -----Original Message-----
> From: Jim Whitehead [mailto:ejw@cse.ucsc.edu]
> Sent: 21 June 2001 00:50
> To: WebDAV WG
> Subject: RE: Status code for creating lock-null resource

[snipped]

> > > 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.  Moving the server state of an 'unmapped-URL where 
> the immediate
> > parent exists' from no resource to a resource should, IMHO, 
> respond with
> > 201 Created.
> 
> This makes sense to me. My concern is that it would still be 
> nice for the
> first PUT after a lock-null is created to also return a 201.
> 
> - Jim
> 

Just double checked MKCOL. It of course returns 201 upon success, never 200.
So your above suggestion would match MKCOL as well. Assuming no errors,
expected behaviour would be:

1) Client issues LOCK, "creating" an LNR, returns 201.
2) Client issues PUT or MKCOL on the LNR, either of which return 201.

Which of course is consistent, duh.

Regards

Shaun Hall
Xerox Europe
Received on Thursday, 21 June 2001 04:40:57 GMT

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