Apache-Wyrd
view release on metacpan or search on metacpan
version.
Apache::Wyrd is distributed in the hope that it will be useful, but
WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
General Public License for more details.
=head2 (GENERALLY) UNIX-Only
This software has only tested under Linux and Darwin, but should work
for any *nix-style system. This software is not intended for use on
windows or other delicate glassware.
=head2 Cross Scripting
This software is meant to run on mod_perl, which, unlike PHP for example, is
not a separate language. It is a direct interface to Apache internals.
Although Apache::Wyrd supports multiple namespaces and consequently,
multiple sites on different virtual server definitions of an Apache
installation, it has not, and the author believes cannot, be designed to
prevent cross-scripting attacks. Consequently, Apache::Wyrd is not
Wyrd/Handler.pm view on Meta::CPAN
=head1 BUGS/CAVEATS/RESERVED METHODS
=head2 FREE SOFTWARE
Standard warning about GNU GPL software. See LICENSE under the documentation
for Apache::Wyrd
=head2 (GENERALLY) UNIX-Only
This software has only tested under Linux and Darwin, but should work
for any *nix-style system. This software is not intended for use on
windows or other delicate glassware.
=head1 AUTHOR
Barry King E<lt>wyrd@nospam.wyrdwright.comE<gt>
=head1 SEE ALSO
=over
Wyrd/Site.pod view on Meta::CPAN
self-maintaining. They are kept separate from the other modules in the
Apache::Wyrd hierarchy because they follow a more rigid set of conventions
on site construction than the other modules, and would introduce
inflexibility to the other Modules if more closely integrated.
As a whole, they represent the more functional aspects of a "house style",
which makes several assumptions:
=over
=item The host system is Unix-like, following a process model
=item The apache version is < 2.0 with multiple listening processes
=item There is no more than one Wyrd namespace per virtual host
=item The site is organized hierarchically in one or more trees
=item Each tree is a "section" with a single parent node as its root
=item Each tree node is either a leaf or a joint between one or more
( run in 0.547 second using v1.01-cache-2.11-cpan-39bf76dae61 )