You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs-cvs@perl.apache.org by st...@apache.org on 2003/08/08 22:59:45 UTC
cvs commit: modperl-docs/src/docs/2.0/api config.cfg
stas 2003/08/08 13:59:45
Modified: src/docs/2.0/api config.cfg
Added: src/docs/2.0/api/Apache porting.pod
Log:
doc for the new module Apache::porting
Revision Changes Path
1.1 modperl-docs/src/docs/2.0/api/Apache/porting.pod
Index: porting.pod
===================================================================
=head1 NAME
Apache::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;
# or httpd.conf
PerlModule Apache2
PerlModule Apache::porting
=head1 Description
C<Apache::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 trap calls to methods that are no longer in the
mod_perl 2.0 API and tell what should be used instead if at all. If
you attempts to use mod_perl 2.0 methods without first loading the
modules that contain them, it will tell you which modules you need to
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.
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
explained in the L<Culprits|/Culprits> section.
It relies heavily on
C<L<ModPerl::MethodLookup|docs::2.0::api::ModPerl::MethodLookup>>.
which can also be used manually to lookup things.
=head1 Culprits
C<Apache::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>
only during the I<child_init> phase, when child processes start. As a
result it can't help you with things that get preloaded at the server
startup.
If you know how to resolve this problem, please let us know. To
reproduce the problem try to use an earlier phase,
e.g. C<PerlPostConfigHandler>:
Apache->server->push_handlers(PerlPostConfigHandler => \&porting_autoload);
=cut
1.27 +1 -0 modperl-docs/src/docs/2.0/api/config.cfg
Index: config.cfg
===================================================================
RCS file: /home/cvs/modperl-docs/src/docs/2.0/api/config.cfg,v
retrieving revision 1.26
retrieving revision 1.27
diff -u -r1.26 -r1.27
--- config.cfg 9 Jun 2003 05:55:43 -0000 1.26
+++ config.cfg 8 Aug 2003 20:59:45 -0000 1.27
@@ -25,6 +25,7 @@
Apache/FilterRec.pod
Apache/Log.pod
Apache/PerlSections.pod
+ Apache/porting.pod
Apache/RequestRec.pod
Apache/RequestUtil.pod
Apache/ServerUtil.pod
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org