perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject cvs commit: modperl-docs/src/docs/2.0/user/handlers server.pod
Date Mon, 01 Mar 2004 22:41:46 GMT
stas        2004/03/01 14:41:46

  Modified:    src/docs/2.0/user/handlers server.pod
  Log:
  explain what are the pool arguments
  
  Revision  Changes    Path
  1.12      +26 -0     modperl-docs/src/docs/2.0/user/handlers/server.pod
  
  Index: server.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/server.pod,v
  retrieving revision 1.11
  retrieving revision 1.12
  diff -u -u -r1.11 -r1.12
  --- server.pod	19 Jan 2004 20:04:32 -0000	1.11
  +++ server.pod	1 Mar 2004 22:41:46 -0000	1.12
  @@ -222,6 +222,32 @@
   
     PerlOpenLogsHandler MyApache::StartupLog::open_logs
   
  +The pool arguments in this phase and
  +C<L<PerlPostConfigHandler|/PerlPostConfigHandler>> are:
  +
  +=over
  +
  +=item *
  +
  +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.
  +
  +=item *
  +
  +C<$log_pool> is a global pool's sub-pool, therefore its life-span is
  +the same as the Apache program's one.
  +
  +META: what is it good for if it lives the same life as conf pool?
  +
  +=item *
  +
  +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. So you will want to use that pool for doing
  +anything that can be discarded before the requests processing starts.
  +
  +=back
   
   
   =head2 PerlPostConfigHandler
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org


Mime
View raw message