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 ra...@apache.org on 2005/04/03 01:39:59 UTC
svn commit: r159850 - in perl/modperl/docs/trunk/src/docs/2.0/user/intro:
overview.pod start_fast.pod
Author: randyk
Date: Sat Apr 2 15:39:58 2005
New Revision: 159850
URL: http://svn.apache.org/viewcvs?view=rev&rev=159850
Log:
s/Apache/Apache2/
Modified:
perl/modperl/docs/trunk/src/docs/2.0/user/intro/overview.pod
perl/modperl/docs/trunk/src/docs/2.0/user/intro/start_fast.pod
Modified: perl/modperl/docs/trunk/src/docs/2.0/user/intro/overview.pod
URL: http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/2.0/user/intro/overview.pod?view=diff&r1=159849&r2=159850
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/intro/overview.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/intro/overview.pod Sat Apr 2 15:39:58 2005
@@ -108,7 +108,7 @@
Filtering of Perl modules output has been possible for years since
tied filehandle support was added to Perl. There are several modules,
-such as C<Apache::Filter> and C<Apache::OutputChain> which have been
+such as C<Apache2::Filter> and C<Apache::OutputChain> which have been
written to provide mechanisms for filtering the C<STDOUT> stream.
There are several of these modules because no one's approach has quite
been able to offer the ease of use one would expect, which is due
@@ -218,14 +218,14 @@
the C<Perl*Handler> configuration directives. By simply adding this
configuration:
- PerlModule Apache::Foo
+ PerlModule Apache2::Foo
-C<Apache::Foo> can register hooks itself at server startup:
+C<Apache2::Foo> can register hooks itself at server startup:
- Apache::Hook->add(PerlAuthenHandler => \&authenticate,
- Apache::Hook::MIDDLE);
- Apache::Hook->add(PerlLogHandler => \&logger,
- Apache::Hook::LAST);
+ Apache2::Hook->add(PerlAuthenHandler => \&authenticate,
+ Apache2::Hook::MIDDLE);
+ Apache2::Hook->add(PerlLogHandler => \&logger,
+ Apache2::Hook::LAST);
META: Not implemented yet (API will change?)
@@ -269,11 +269,11 @@
there are two approaches. A module can "subclass" directive handlers,
saving a copy of the data for itself, then returning B<DECLINE_CMD> so
the other modules are also handed the info. Or, the
-C<$Apache::PerlSections::Save> variable can be set to save
-E<lt>PerlE<gt> configuration in the C<%Apache::ReadConfig::>
+C<$Apache2::PerlSections::Save> variable can be set to save
+E<lt>PerlE<gt> configuration in the C<%Apache2::ReadConfig::>
namespace. Both methods are rather kludgy, version 2.0 provides a
L<Perl interface to the Apache configuration
-tree|docs::2.0::user::config::config/Perl_Interface_to_the_Apache_Configuration_Tree>.
+tree|docs::2.0::user::config::config/Perl_Interface_to_the_Apache2_Configuration_Tree>.
=back
@@ -589,12 +589,12 @@
module|docs::2.0::user::porting::compat> can be used.
In mod_perl 2.0 the APR API resides in the C<APR::> namespace, and
-obviously the C<Apache::> namespace is mapped to the Apache API.
+obviously the C<Apache2::> namespace is mapped to the Apache API.
And in the case of C<APR>, it is possible to use C<APR> modules
outside of Apache, for example:
- % perl -MApache2 -MAPR -MAPR::UUID -le 'print APR::UUID->new->format'
+ % perl -MAPR -MAPR::UUID -le 'print APR::UUID->new->format'
b059a4b2-d11d-b211-bc23-d644b8ce0981
The mod_perl 2.0 generator is a custom suite of modules specifically
@@ -720,7 +720,7 @@
=item *
-Inlined C<Apache::*.xs> calls
+Inlined C<Apache2::*.xs> calls
=item *
Modified: perl/modperl/docs/trunk/src/docs/2.0/user/intro/start_fast.pod
URL: http://svn.apache.org/viewcvs/perl/modperl/docs/trunk/src/docs/2.0/user/intro/start_fast.pod?view=diff&r1=159849&r2=159850
==============================================================================
--- perl/modperl/docs/trunk/src/docs/2.0/user/intro/start_fast.pod (original)
+++ perl/modperl/docs/trunk/src/docs/2.0/user/intro/start_fast.pod Sat Apr 2 15:39:58 2005
@@ -57,17 +57,13 @@
LoadModule perl_module modules/mod_perl.so
-Next, tell Perl where to find mod_perl2 libraries:
-
- PerlModule Apache2
-
There are many other configuration options which you can find in the
L<configuration manual|docs::2.0::user::config::config>.
If you want to run mod_perl 1.0 code on mod_perl 2.0 server enable the
compatibility layer:
- PerlModule Apache::compat
+ PerlModule Apache2::compat
For more information see: L<Migrating from mod_perl 1.0 to mod_perl
2.0|docs::2.0::user::porting::compat>.
@@ -140,17 +136,17 @@
response handler similar to the registry script from the previous
section:
- #file:MyApache/Rocks.pm
+ #file:MyApache2/Rocks.pm
#----------------------
- package MyApache::Rocks;
+ package MyApache2::Rocks;
use strict;
use warnings;
- use Apache::RequestRec ();
- use Apache::RequestIO ();
+ use Apache2::RequestRec ();
+ use Apache2::RequestIO ();
- use Apache::Const -compile => qw(OK);
+ use Apache2::Const -compile => qw(OK);
sub handler {
my $r = shift;
@@ -158,13 +154,13 @@
$r->content_type('text/plain');
print "mod_perl 2.0 rocks!\n";
- return Apache::OK;
+ return Apache2::OK;
}
1;
-Save the code in the file I<MyApache/Rocks.pm>, somewhere where
+Save the code in the file I<MyApache2/Rocks.pm>, somewhere where
mod_perl can find it. For example let's put it under
-I</home/httpd/httpd-2.0/perl/MyApache/Rocks.pm>, and we tell mod_perl
+I</home/httpd/httpd-2.0/perl/MyApache2/Rocks.pm>, and we tell mod_perl
that I</home/httpd/httpd-2.0/perl/> is in C<@INC>, via a startup file
which includes just:
@@ -179,7 +175,7 @@
<Location /rocks>
SetHandler perl-script
- PerlResponseHandler MyApache::Rocks
+ PerlResponseHandler MyApache2::Rocks
</Location>
Now restart the server and issue a request to
---------------------------------------------------------------------
To unsubscribe, e-mail: docs-cvs-unsubscribe@perl.apache.org
For additional commands, e-mail: docs-cvs-help@perl.apache.org