Apache::PAR::Registry - Apache::Registry subclass which serves Apache::Registry scripts to clients from within .par files.
A sample configuration (within a web.conf) is below:
Alias /myapp/cgi-perl/ ##PARFILE##/ <Location /myapp/cgi-perl> Options +ExecCGI SetHandler perl-script PerlHandler Apache::PAR::Registry PerlSetVar PARRegistryPath registry/ </Location>
Subclass of Apache::Registry (or ModPerl::Registry) to serve Apache::Registry scripts to clients from within .par files. Registry scripts should continue to operate as they did before when inside a .par archive.
To use, add Apache::PAR::Registry into the Apache configuration, either through an Apache configuration file, or through a web.conf file (discussed in more detail in the Apache::PAR manpage.)
Options +ExecCGI must be turned on in the configuration in order to serve Registry scripts.
.par files must be executable by the web server user in order to serve Registry scripts.
File modification testing is performed on the script itself. Otherwise modifying the surrounding package should not cause mod_perl to reload the module.
Modules can be loaded from within the .par archive as if they were physically on the filesystem. However, because of the way PAR.pm works, your scripts can also load modules within other .par packages, as well as modules from your @INC.
By default, scripts are served under the script/ directory within a .par archive. This value can be changed using the PARRegistryPath variable, for instance:
PerlSetVar PARRegistryPath registry/
NOTE: The default location has changed with Apache::PAR 0.20. Previously, the default location for Registry scripts was the scripts/ directory. To continue to use the old path in an archive, set the following in a web.conf:
PerlSetVar PARRegistryPath scripts/
None by default.
Nathan Byrd, <firstname.lastname@example.org>
Copyright 2002 by Nathan Byrd <email@example.com>.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.