geoff       2003/08/12 11:06:05

  Modified:    src/docs/2.0/user/handlers intro.pod
               src/docs/2.0/user/porting compat.pod
  Log:
  document new stacked handler behavior in porting
  document.  fix PerlChildExitHandler run-type.
  Submitted by: geoff
  
  Revision  Changes    Path
  1.10      +1 -1      modperl-docs/src/docs/2.0/user/handlers/intro.pod
  
  Index: intro.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/handlers/intro.pod,v
  retrieving revision 1.9
  retrieving revision 1.10
  diff -u -r1.9 -r1.10
  --- intro.pod 18 Jul 2003 10:42:48 -0000      1.9
  +++ intro.pod 12 Aug 2003 18:06:05 -0000      1.10
  @@ -238,7 +238,7 @@
     PerlOpenLogsHandler          RUN_ALL
     PerlPostConfigHandler        RUN_ALL
     PerlChildInitHandler         VOID
  -  PerlChildExitHandler         RUN_ALL
  +  PerlChildExitHandler         VOID
     
     PerlPreConnectionHandler     RUN_ALL
     PerlProcessConnectionHandler RUN_FIRST
  
  
  
  1.19      +20 -0     modperl-docs/src/docs/2.0/user/porting/compat.pod
  
  Index: compat.pod
  ===================================================================
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/user/porting/compat.pod,v
  retrieving revision 1.18
  retrieving revision 1.19
  diff -u -r1.18 -r1.19
  --- compat.pod        5 Aug 2003 06:34:46 -0000       1.18
  +++ compat.pod        12 Aug 2003 18:06:05 -0000      1.19
  @@ -1177,6 +1177,26 @@
   handler has to be a method.
   
   
  +=head2 Stacked Handlers
  +
  +Both mod_perl 1.0 and 2.0 support the ability to register more
  +than one handler in each runtime phase, a feature known as
  +stacked handlers.  For example,
  +
  +  PerlAuthenHandler My::First My::Second
  +
  +The behavior of stacked Perl handlers differs between mod_perl 1.0
  +and 2.0.  In 2.0, mod_perl respects the run-type of the underlying
  +hook - it does not run all configured Perl handlers for each phase
  +but instead behaves in the same way as Apache does when multiple
  +handlers are configured, respecting (or ignoring) the return 
  +value of each handler as it is called.
  +
  +See L<Single Phase's Multiple Handlers
  
+Behavior|docs::2.0::user::handlers::intro/Single_Phase_s_Multiple_Handlers_Behavior>
  +for a complete description of each hook and its run-type.
  +
  +
   =head1 C<Apache::src>
   
   For those who write 3rd party modules using XS, this module was used
  
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to