apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Orton <jor...@redhat.com>
Subject Re: Problems with DSOs and Pools
Date Mon, 14 Aug 2006 09:38:26 GMT
On Fri, Aug 11, 2006 at 12:42:32PM -0400, Garrett Rooney wrote:
> The timeline for this sort of thing looks like this:
> 1. Create application pool (global scope).
> 2. In another global pool open up a DSO.
> 3. Call a function defined in the DSO, passing in your application pool.
> 4. The function inside the DSO registers a cleanup on the application pool.

"don't do that" would be the obvious (if flippant) answer.  Can you not 
provide some interface for the DSO to clean itself up before it is 
unloaded?  e.g. the DSO could register a cleanup on the DSO-owning-pool 
which will kill any other "global" cleanups it might have registered?


View raw message