Stas Bekman wrote:
I've looked at the httpd source code, ptemp is destroyed at the end of the post_config phase. So we should use it for any temporary things that don't need to live through the config.
So hook-config is the perfect case for ptemp.
that's fine, but how do you get to it? for instance, we can create the hook_order table using ptemp by calling the init in pre-config. however, there is no easy way to get to ptemp from modperl_cmd, where the data going into hook_order will be generated - all you have is pconf or parms->pool at that point.
or are you planning on adding a set of hooks to get to ptemp?
I think we need a hook to access it. Have a static global, init it from pre_config and use it when needed.
Here is a short summary of pool life-times:
C<$log_pool> is a global pool's sub-pool, therefore its life-span is the same as the Apache program's one.
C<$conf_pool> is the main process sub-pool, therefore its life-span is the same as the main process's one. The main process is a sub-pool of the global pool.
C<$temp_pool> is a C<$conf_pool> subpool, created before the config phase, lives through the open_logs phase and get destroyed after the post_config phase.
The ancestry tree:
global
| |
main_process log
|
conf
|
temp__________________________________________________________________ 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]
