On 6/8/07, Daniel Rall <dlr@collab.net> wrote:
> I believe it's just a side-effect of the current RA loader
> implementation. IIRC, people have looked at changing this a few times
> in the past, but didn't get any traction. The RA loader isn't a ton
> of code -- it should be pretty easy to just toss the existing one an
> re-write it from scratch, if need be.
One problem with this. RA libraries are chosen by two APIs:
svn_ra_open[2] and svn_ra_get_ra_library. svn_ra_open[2] gets a
config hash, so it could use the servers file to decide which library
to use. But the compatibility interface svn_ra_get_ra_library does
not get it. If a program which uses svn_ra_get_ra_library (using the
pre-1.2 API) is run against a Subversion client linking both ra_dav
and ra_serf, I don't see any way for the config files to affect which
is chosen, so even though your config file might say "use serf!", the
internal fact that the program you're running uses the pre-1.2 API
will prevent your configuration from working.
How big of an issue is this? Is it acceptable to implement
user-configurable RA library support and have it be ignored for
programs written against the pre-1.2 API? (Note that a user of such a
program may have no idea what APIs it uses...)
--dave
--
David Glasser | glasser_at_mit.edu | http://www.davidglasser.net/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jun 9 23:38:47 2007