[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-03-19 13:00:58 CET

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.

(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?)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 19 13:02:14 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.