On 2/6/06, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> In my work with ra_serf, I've come across the problem that we really
> can't have multiple RA layers declare for the same scheme gracefully.
> The current RA implementation will treat a NULL init value to be 'load
> this as a DSO' - if the DSO load fails, then it will never try another
> RA layer. load_ra_module returns a fatal error - on my machine it
> figures out the library isn't there only in apr_dso_sym not in
> apr_dso_load.
>
> I'm not quite sure if it should be even trying the DSO load at all or
> should it try other ra_libraries instead?
>
> My first thought is that it shouldn't try at all. So, I'm using this
> patch which moves the conditionals to encompass the entire scheme
> definition - this way, it'll never 'see' ra_dav, but will try to load
> ra_serf.
It seems kind of odd that it tries to load them if they weren't
compiled at first, but then again I'm not really clear how the people
who build dso ra layers actually make all that work with the build
system, so perhaps that makes more sense from that perspective.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 7 02:04:56 2006