Greg Stein <gstein@lyra.org> writes:
> ra_svn had a *ton* of prior experience to work with, and a lot of code to
> leverage. Did it have to revamp its editor usage a few times? Nope. Change
> the reporter interface? Nope. Heck... deal with the introduction of the
> reporter interface? Nah. etc etc. Of course, it also had the benefit of a
> single purpose protocol to radically simplify things. No question there, but
> do I have a Python or Perl library that can talk to svnserve? Nope. To
> mod_dav_svn? Hell ya. And a C library, and a Ruby library, and ...
What he said.
Ra_svn hasn't gotten the workout that ra_dav has yet. We've been
abusing our mod_dav_svn server for more than a year now, and other
people have been abusing theirs -- some of whom have very active
repositories. That's the reason we've found all these bugs.
Trying to measure ra_svn's stability at this point is silly. If we
had taken an informal poll about ra_dav's stability after the first
month of self-hosting, we would have come to the same conclusion now
being claimed for ra_svn. A lot of these edge-case bugs came out
later.
(Don't mean to impugne Greg Hudson's fine work, of course; I think
ra_svn is *great* and am planning to try it out for personal projects.
I'm just saying it hasn't yet gotten the exposure that ra_dav has, and
therefore there's less information with which to evaluate it, both in
terms of latent bugs and missing features. Six months from now, we'll
know a lot more.)
-K
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Jan 16 06:36:51 2003