perl-docs-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: modperl-docs/src/docs/2.0/api/Apache porting.pod
Date Fri, 08 Aug 2003 21:27:15 GMT
stas        2003/08/08 14:27:15

  Modified:    src/docs/2.0/api/Apache porting.pod
  how Apache::porting tells about the problems,
  Revision  Changes    Path
  1.2       +9 -0      modperl-docs/src/docs/2.0/api/Apache/porting.pod
  Index: porting.pod
  RCS file: /home/cvs/modperl-docs/src/docs/2.0/api/Apache/porting.pod,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- porting.pod	8 Aug 2003 20:59:45 -0000	1.1
  +++ porting.pod	8 Aug 2003 21:27:15 -0000	1.2
  @@ -12,6 +12,8 @@
     PerlModule Apache2
     PerlModule Apache::porting
  +  # now issue requests and look at the error_log file for hints
   =head1 Description
   C<Apache::porting> helps to port mod_perl 1.0 code to run under
  @@ -23,6 +25,13 @@
   load. Finally if your code tries to load modules that no longer exist
   in mod_perl 2.0 it'll also tell you what are the modules that should
   be used instead.
  +C<Apache::porting> communicates with users via the I<error_log>
  +file. Everytime it traps a problem, it logs the solution (if it finds
  +one) to the error log file. If you use this module coupled with
  +C<L<Apache::Reload|docs::2.0::api::Apache::Reload>> you will be able
  +to port your applications quickly without needing to restart the
  +server on every modification.
   It starts to work only when child process start and doesn't work for
   the code that gets loaded at the server startup. This limitation is

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message