Greg Hudson <ghudson@MIT.EDU> writes:
> But I don't want svnserve handling that full complexity. It's my
> position that apr and apr-util should be doing all the heavy lifting of
> writing a network daemon, and Subversion should simply be taking
> advantage of it. There's already too much code in svnserve and ra_svn
> which isn't specific to Subversion.
>
> Of course, actually extending apr and apr-util to do that heavy lifting
> requires careful design and no small amount of work. So the current
> reality is that svnserve is a rather anemic daemon.
Hmmm. You know...
In the past, we've handled this situation by writing the APR
implementations in Subversion -- that is, putting functions whose
names begin with "apr_" into the Subversion code (protected by
#ifundef in the usual way). Then, when all the kinks are worked out,
we have code that's much closer to being droppable into APR/APU then
we otherwise would have had.
So factoring out some of this svnserve stuff now might make sense,
even if the factored out portion continues to live in the Subversion
repository for the time being.
Just a thought,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 28 21:31:21 2005