Re: Locking server implementation: libsvn_repos or libsvn_fs

It seems like most of the smaller issues have dropped out of this
thread. Allow me to oversimplify.

* The remaining 'big' argument for locks-in-fs is "it's more convenient
for
   callers."

* The remaining big argument for locks-in-repos is "it's easier to
   implement".

* Everyone wants to implement the lock-table (or tree) without using a
   database, regardless of whether we do locks-in-fs or locks-in-repos.

* How 'svnadmin dump' deals with locks is also independent of where
   locks are implemented. Either we tell people to back up the locks
   data manually (like we do with hooks, authz file, etc), or we
   augment the dump format and make svnadmin grab the lock data,
   wherever it may be.

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