![]() |
Home / Documentation / 2.0 / | ![]() |
||
![]() ![]() ![]() |
||||
mod_perl APIs | ||||
![]() |
|
||
The Apache::, APR:: and ModPerl:: namespaces APIs for mod_perl 2.0
Apache::Access
provides the Perl API for Apache request object.Apache::compat
provides mod_perl 1.0 compatibility layer and can be
used to smooth the transition process to mod_perl 2.0.Apache::Directive
allows its users to search and navigate the
internal Apache configuration.Apache::Filter
provides the Perl API for Apache 2.0 filtering
framework.Apache::Log
provides the Perl API for Apache logging methods.<Perl >
...</Perl>
sections, it is possible
to configure your server entirely in Perl.Apache::RequestIO
provides the API to perform IO on the Apache request object.Apache::RequestRec
provides the Perl API for Apache request object.Apache::ServerUtil
provides the Perl API for Apache server object.Apache::SubProcess
provides the Perl API for running and
communicating with processes spawned from mod_perl handlers.APR::PerlIO
implements a Perl IO layer using APR's file
manipulation as its internals.APR::Table
allows its users to manipulate opaque string-content
tables.ModPerl::MethodLookup
provides the Perl API for finding
module names which contain methods in question and other helper
functions, like figuring out what methods defined by some module, or
what methods can be called on a given object.ModPerl::MM
is a "subclass" of ExtUtils::MakeMaker
for mod_perl
2.0, to a degree of sub-classability of ExtUtils::MakeMaker
. http://example.com/perl/test.pl
will be
compiled as the body of a Perl subroutine and executed. Each child
process will compile the subroutine once and store it in memory. It
will recompile it whenever the file (e.g. test.pl in our example)
is updated on disk. Think of it as an object oriented server with
each script implementing a class loaded at runtime.ModPerl::RegistryBB
is similar to ModPerl::Registry
, but does
the bare minimum (mnemonic: BB = Bare Bones) to compile a script file
once and run it many times, in order to get the maximum
performance. Whereas ModPerl::Registry
does various checks,
which add a slight overhead to response times.ModPerl::RegistryCooker
is used to create flexible and overridable
registry modules which emulate mod_cgi for Perl scripts. The concepts
are discussed in the manpage of the following modules:
ModPerl::Registry
, ModPerl::Registry
and
ModPerl::RegistryBB
.ModPerl::RegistryCooker
, at server startup. The
script's handler routine is compiled by the parent server, of which
children get a copy and thus saves some memory by initially sharing
the compiled copy with the parent and saving the overhead of script's
compilation on the first request in every httpd instance.ModPerl::Util
provides mod_perl 2.0 util functions.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.Apache::Reload
reloads modules that change on the disk.ModPerl::BuildMM
is a "subclass" of ModPerl::MM
used for
building mod_perl 2.0. Refer to
ModPerl::MM
manpage.See
search.cpan.org
or www.perldoc.com for
documentation of the 3rd party Apache::
modules.
|
![]() |
![]() ![]() ![]() |