[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: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2005-03-17 09:58:02 CET

Ben Collins-Sussman wrote:
> Even though it's very late in the game, there are some critical
> decisions we need to make about locking features. They tend to
> cascade out from each other.
> * Fact: libsvn_fs allows already locks on non-existent paths. This
> feature exists to be interoperable with generic DAV clients. In DAV
> parlance, such things are called 'lock-null' resources. That is:
> they're 'null' resources (they don't exist), but are still locked.

Lock null resources are deprecated in RFC2518bis (see [1] and [2]), and
as far as I can tell, no generic client requires them.

What *is* needed is the ability to LOCK an unmapped resource. However,
it's completely sufficient to implement this by creating an empty placew
holder resource.


   LOCK unmapped

can be exactly the same as

   PUT unmapped
   Content-Length: 0

followed by

   LOCK unmapped

> ...

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
Received on Thu Mar 17 09:59:16 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.