Locking: regarding fsfs

Okay, after a couple of weeks, I think we've hammered out a reasonable
implementation of locks in BDB. Huge thanks to striker and cmpilato
(and brane, for preventing us from going down a bad road!)

The locking branch compiles now, and you can play with the BDB
repository locks using the three new 'svnadmin' commands. I'm gonna
start writing some new fs-tests (the C tests) to check that locks are
being properly enforced during write operations, both on-the-fly and at
final commit time. The fsfs implementation of locks will be able to
use the same tests too.

Speaking of fsfs, can I entice anyone to start working on it? ghudson?
  jpieper? Or somebody else dying to learn the internals of fsfs?

A lot of the groundwork has already been laid out for you:

    * multiple passes/cleanups the 5 new API signatures and their
promises
    * new shareable APIs to pass a username & lock-tokens into an fs_t
    * new shareable APIs to verify that locks are usable by the committer
    * a BDB reference implementation to imitate, if need be. :-)
    * coming soon, a test suite.

A chance to write new code is pretty rare -- this is your chance to
have some fun.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Nov 19 18:20:34 2004