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

Re: Locking server implementation: libsvn_repos or libsvn_fs

From: Greg Hudson <ghudson_at_MIT.EDU>
Date: 2004-10-29 17:08:36 CEST

On Fri, 2004-10-29 at 10:49, Ben Collins-Sussman wrote:
> I'm not worried about this. If we decide to implement locks in the
> repos library, we can use "some random dbm"... whatever happens to be
> picked up by APR. I believe that APR *always* picks up some system dbm
> library. There's a whole apr_dbm_*() set of APIs, and mod_dav_svn
> already uses them to manage a private table in repos/dav/.... even when
> the repository itself is fsfs.

"Some random dbm" won't work over NFS or another remote filesystem.
mod_dav_svn does not keep its activity db inside the repository.

It's possible, and relatively straightforward, to make the locking table
work using just the regular old filesystem. Just create a skeleton
directory tree mirroring the part of the repository which has active
locks. Store lock tokens at the leaves. URL-encode pathnames so that
encoding issues don't come into play.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 29 17:09:09 2004

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.