Re: Locking non-existent paths. Time to discuss.

Ben Collins-Sussman wrote:
> On Mar 19, 2005, at 3:26 AM, C. Michael Pilato wrote:
>
>>
>> Say what?! Julian, will you please explain what is and isn't needed
>> support-wise across the following four areas of LOCKNULL support:
>>
>> - LOCK on a NULL resource
>> - UNLOCK on a NULL resource
>> - PROPFIND on a LOCKNULL resource
>> - Revelation of immediate LOCKNULL children of normal collections
>
>
> Ah, I think I see what Julian is saying.
>
> If RFC2518bis expects a LOCK on a NULL resource to be handled as a
> 0-byte PUT, then I guess a 2518bis-conformant client *should* expect to
> see the object listed in the parent. It's no longer a NULL resource.

Right.

> (It sure would be nice to be able to read 2518bis! I can't find any
> link to it on www.webdav.org, nor does a google search bring it up. Is
> it some secret thing still?)

That's strange, Google located the copy on our page, see:

<http://greenbytes.de/tech/webdav/#draft-ietf-webdav-rfc2518bis>

And yes, webdav.org doesn't link to it and the draft hasn't been updated
for over 8 months. Please complain to the working group chairs and
authors :-)

Best regards, Julian

-- 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org