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

Re: Adding a no-op LOCK to mod_dav_svn

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2003-01-04 04:56:31 CET

On Friday, January 3, 2003, at 10:36 PM, Justin Erenkrantz wrote:
> The strategy that I've considered is doing a shared hash table/list of
> LOCKed resources across all httpd's. That gets us complete compliance
> with the DAV spec. DAV specifically allows locks to disappear at any
> time for any reason - a server restart can toss locks - there is no
> requirement on persistence. Therefore, a shared memory hash table (or
> something like that) isn't a mis-implementation of the DAV spec.

this sounds much more reasonable to me than a 'no-op LOCK
implementation' did at first ;-)

as long as we're following the DAV spec, this seems like it can only be
a good thing.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jan 4 04:57:14 2003

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.