install::TempContent::Objects::mod_perl-2.0.9::docs::apiUserdContribuinstall::TempContent::Objects::mod_perl-2.0.9::docs::api::ModPerl::PerlRun(3)NAME
ModPerl::PerlRun - Run unaltered CGI scripts under mod_perl
Synopsis
# httpd.conf
PerlModule ModPerl::PerlRun
Alias /perl-run/ /home/httpd/perl/
<Location /perl-run>
SetHandler perl-script
PerlResponseHandler ModPerl::PerlRun
PerlOptions +ParseHeaders
Options +ExecCGI
</Location>
Description
META: document that for now we don't chdir() into the script's dir, because it affects the whole process under threads.
"ModPerl::PerlRunPrefork" should be used by those who run only under prefork MPM.
Special Blocks
"BEGIN" Blocks
When running under the "ModPerl::PerlRun" handler "BEGIN" blocks behave as follows:
o "BEGIN" blocks defined in scripts running under the "ModPerl::PerlRun" handler are executed on each and every request.
o "BEGIN" blocks defined in modules loaded from scripts running under "ModPerl::PerlRun" (and which weren't already loaded prior to the
request) are executed on each and every request only if those modules declare no package. If a package is declared "BEGIN" blocks will
be run only the first time each module is loaded, since those modules don't get reloaded on subsequent requests.
See also "BEGIN" blocks in mod_perl handlers.
"CHECK" and "INIT" Blocks
Same as normal mod_perl handlers.
"END" Blocks
Same as "ModPerl::Registry".
Authors
Doug MacEachern
Stas Bekman
See Also
"ModPerl::RegistryCooker" and "ModPerl::Registry".
perl v5.18.22install::TempContent::Objects::mod_perl-2.0.9::docs::api::ModPerl::PerlRun(3)
Check Out this Related Man Page
install::TempContent::Objects::mod_perl-2.0.9::docs::apiUserdCinstall::TempContent::Objects::mod_perl-2.0.9::docs::api::ModPerl::RegistryCooker(3)NAME
ModPerl::RegistryCooker - Cook mod_perl 2.0 Registry Modules
Synopsis
# shouldn't be used as-is but sub-classed first
# see ModPerl::Registry for an example
Description
"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" has two purposes:
o Provide ingredients that can be used by registry sub-classes
o Provide a default behavior, which can be overriden in sub-classed
META: in the future this functionality may move into a separate class.
Here are the current overridable methods:
META: these are all documented in RegistryCooker.pm, though not using pod. please help to port these to pod and move the descriptions here.
o new()
create the class's object, bless it and return it
my $obj = $class->new($r);
$class -- the registry class, usually "__PACKAGE__" can be used.
$r -- "Apache2::Request" object.
default: new()
o init()
initializes the data object's fields: "REQ", "FILENAME", "URI". Called from the new().
default: init()
o default_handler()
default: default_handler()
o run()
default: run()
o can_compile()
default: can_compile()
o make_namespace()
default: make_namespace()
o namespace_root()
default: namespace_root()
o namespace_from()
If "namespace_from_uri" is used and the script is called from the virtual host, by default the virtual host name is prepended to the
uri when package name for the compiled script is created. Sometimes this behavior is undesirable, e.g., when the same (physical) script
is accessed using the same path_info but different virtual hosts. In that case you can make the script compiled only once for all
vhosts, by specifying:
$ModPerl::RegistryCooker::NameWithVirtualHost = 0;
The drawback is that it affects the global environment and all other scripts will be compiled ignoring virtual hosts.
default: namespace_from()
o is_cached()
default: is_cached()
o should_compile()
default: should_compile()
o flush_namespace()
default: flush_namespace()
o cache_table()
default: cache_table()
o cache_it()
default: cache_it()
o read_script()
default: read_script()
o shebang_to_perl()
default: shebang_to_perl()
o get_script_name()
default: get_script_name()
o chdir_file()
default: chdir_file()
o get_mark_line()
default: get_mark_line()
o compile()
default: compile()
o error_check()
default: error_check()
o strip_end_data_segment()
default: strip_end_data_segment()
o convert_script_to_compiled_handler()
default: convert_script_to_compiled_handler()
Special Predefined Functions
The following functions are implemented as constants.
o NOP()
Use when the function shouldn't do anything.
o TRUE()
Use when a function should always return a true value.
o FALSE()
Use when a function should always return a false value.
Sub-classing Techniques
To override the default "ModPerl::RegistryCooker" methods, first, sub-class "ModPerl::RegistryCooker" or one of its existing sub-classes,
using "use base". Second, override the methods.
Those methods that weren't overridden will be resolved at run time when used for the first time and cached for the future requests. One way
to to shortcut this first run resolution is to use the symbol aliasing feature. For example to alias "ModPerl::MyRegistry::flush_namespace"
as "ModPerl::RegistryCooker::flush_namespace", you can do:
package ModPerl::MyRegistry;
use base qw(ModPerl::RegistryCooker);
*ModPerl::MyRegistry::flush_namespace =
&ModPerl::RegistryCooker::flush_namespace;
1;
In fact, it's a good idea to explicitly alias all the methods so you know exactly what functions are used, rather then relying on the
defaults. For that purpose "ModPerl::RegistryCooker" class method install_aliases() can be used. Simply prepare a hash with method names in
the current package as keys and corresponding fully qualified methods to be aliased for as values and pass it to install_aliases().
Continuing our example we could do:
package ModPerl::MyRegistry;
use base qw(ModPerl::RegistryCooker);
my %aliases = (
flush_namespace => 'ModPerl::RegistryCooker::flush_namespace',
);
__PACKAGE__->install_aliases(\%aliases);
1;
The values use fully qualified packages so you can mix methods from different classes.
Examples
The best examples are existing core registry modules: "ModPerl::Registry", "ModPerl::Registry" and "ModPerl::RegistryBB". Look at the
source code and their manpages to see how they subclass "ModPerl::RegistryCooker".
For example by default "ModPerl::Registry" uses the script's path when creating a package's namespace. If for example you want to use a uri
instead you can override it with:
*ModPerl::MyRegistry::namespace_from =
&ModPerl::RegistryCooker::namespace_from_uri;
1;
Since the "namespace_from_uri" component already exists in "ModPerl::RegistryCooker". If you want to write your own method, e.g., that
creates a namespace based on the inode, you can do:
sub namespace_from_inode {
my $self = shift;
return (stat $self->[FILENAME])[1];
}
META: when $r->finfo will be ported it'll be more effecient. (stat $r->finfo)[1]
Authors
Doug MacEachern
Stas Bekman
See Also
"ModPerl::Registry", "ModPerl::RegistryBB" and "ModPerl::PerlRun".
perl v5.18.2install::TempContent::Objects::mod_perl-2.0.9::docs::api::ModPerl::RegistryCooker(3)