So your goal is to be able to register some callback to run when the server restarts and not on every child_exit call.
yup. at least if we want to offer the same functionality that mp1 offered.
we also will probably need to implement that pool hack to give the tools to deal with Starting/Restarting.
but now that I'm thinking about it, the interpreter is fully destroyed on restarts, right? that is, a PerlModule will fully load a module both on start _and_ on restart. this wasn't true on static builds in mp1, which is why it was necessary to schedule code callbacks at restart.
for instance, a restart callback could clear a cache or update a global httpd.conf mtime. but if PerlModule re-executes module init code on restart then that could be the mechansim. we just couldn't rely on that in mp1 so we had to use a per-server cleanup.
You mean we don't need to do anything special? Or what do you exactly suggest that we provide?
I'll handle that, I just want to understand what exactly I need to solve and get your feedback on it while I move on with it.
sure. and thanks for doing all that you are. you make the world a better place :)
thanks :)
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
