On Thu, 11 Oct 2001, Philippe M. Chiasson wrote: > Thanks, and might that be slightly more usefull in a macro like :
ok, i've added one for the moment. but in the future, i hope nobody needs it. (see below) > Good. But I discovered another slight annoyance I can't quite resolve. >ap_hook_create_request > is used to create 'r' for every request, I guessed, but there doesn't seem to be a >clean way > to handle destruction/cleaning of that request. So now I am left wondering when/how >to step > in just before a request obj is de-allocated, to free stuff that wasn't allocated >with apr_pools. you can use a cleanup in r->pool. however, i'm thinking in general there should be a cleanup mechanism for the interpreter pool, so cleanups can happen when the interpreter is put back into the pool. because at the moment, pnotes will break if PerlInterpScope is configured to handler or subrequest. because the interpreter will have already been put back into the pool by the time r->pool cleanups are run in these cases. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
