On 8/17/06, Bojan Smojver <[EMAIL PROTECTED]> wrote:
Quoting Garrett Rooney <[EMAIL PROTECTED]>:
> That is in fact what the Subversion code currently does.
I do similar things as well in my code. It just a bit easier as I
control the lot :-)
> The problem
> is that you need to create the global DSO code sufficiently early in
> the application's lifecycle to ensure that it lives longer than all
> other pools during global shutdown. If any other pool will outlive it
> you risk that pool having callbacks set on it that call functions
> defined in the DSO.
At least on Linux, loading/unloading of DSO appears to be a
per-process phenomenon. Maybe we should treat it the same in APR?
I think we're talking about the same thing here. What I want is an
API that says "load this DSO, and don't unload it until we exit".
That would make all my problems (in this particular are anyway) go
away.
-garrett
