Parent Directory
|
Revision Log
|
Patch
--- perl/modperl/docs/trunk/src/docs/2.0/api/Apache2/porting.pod 2005/04/02 21:42:07 159820 +++ perl/modperl/docs/trunk/src/docs/2.0/api/Apache2/porting.pod 2005/04/02 21:53:01 159821 @@ -1,18 +1,16 @@ =head1 NAME -Apache::porting -- a helper module for mod_perl 1.0 to mod_perl 2.0 porting +Apache2::porting -- a helper module for mod_perl 1.0 to mod_perl 2.0 porting =head1 Synopsis # either add at the very beginning of startup.pl - use Apache2; - use Apache::porting; + use Apache2::porting; # or httpd.conf - PerlModule Apache2 - PerlModule Apache::porting + PerlModule Apache2::porting # now issue requests and look at the error_log file for hints @@ -21,7 +19,7 @@ Apache::porting -- a helper module for m =head1 Description -C<Apache::porting> helps to port mod_perl 1.0 code to run under +C<Apache2::porting> helps to port mod_perl 1.0 code to run under mod_perl 2.0. It doesn't provide any back-compatibility functionality, however it knows to trap methods calls that are no longer in the mod_perl 2.0 API and tell what should be used instead if at all. If @@ -31,10 +29,10 @@ load. Finally if your code tries to load 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> +C<Apache2::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 +C<L<Apache2::Reload|docs::2.0::api::Apache2::Reload>> you will be able to port your applications quickly without needing to restart the server on every modification. @@ -53,7 +51,7 @@ which can also be used manually to looku =head1 Culprits -C<Apache::porting> uses the C<UNIVERSAL::AUTOLOAD> function to provide +C<Apache2::porting> uses the C<UNIVERSAL::AUTOLOAD> function to provide its functionality. However it seems to be impossible to create C<UNIVERSAL::AUTOLOAD> at the server startup, Apache segfaults on restart. Therefore it performs the setting of C<UNIVERSAL::AUTOLOAD> @@ -65,7 +63,7 @@ If you know how to resolve this problem, reproduce the problem try to use an earlier phase, e.g. C<PerlPostConfigHandler>: - Apache->server->push_handlers(PerlPostConfigHandler => \&porting_autoload); + Apache2->server->push_handlers(PerlPostConfigHandler => \&porting_autoload); META: Though there is a better solution at work, which assigns AUTOLOAD for each class separately, instead of using UNIVERSAL. See
infrastructure at apache.org | ViewVC Help |
Powered by ViewVC 1.1.26 |