[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: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2005-03-17 10:05:51 CET

Julian Reschke <julian.reschke@gmx.de> writes:

> 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.

Well, that's certainly going to make useless a bunch of work I was
moments away from committing. :-(

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Mar 17 10:10:04 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.