Ports Search

Apache::Profiler is a mod_perl init (and cleanup) handler to profile time taken to process one request. Profiled data is reported to the Apache Log file. It'd be useful to profile some heavy application taking a long time to proceed.

Apache::Session::PHP is an adapter of Apache::Session for PHP::Session

This module is an implementation of Apache::Session. It uses the DBD::SQLite backing store. It requires DBD::SQLite version 1.00 or above, due to its use of SQLite3 API for BLOB support. Also, an extra LastUpdated field is populated with the current time(). There is no need to create the data source file beforehand; this module creates the session table automatically.

Apache::Session::SharedMem is an Apache::Session extension module that stores the session data in Shared memory (so, does exactly what it says on the tin then) using IPC::Cache (and hence IPC::ShareLite).

This module is a simple wrapper around Apache::Session which provides some methods to simplify getting and setting the session id. It can uses cookies to store the session id, or it can look in a provided object for a specific parameter. Alternately, you can simply provide the session id yourself in the call to the session() method. If you're using Mason, you should probably take a look at MasonX::Request::WithApacheSession first, which integrates this module directly into Mason.

From the README file: These modules are used to keep persistent user data across http requests. Apache::Session was designed for use with Apache and mod_perl, but works just as well under CGI and any other web server. Apache::Session is Copyright(c) 1998, 1999 Jeffrey William Baker <jeffrey@kathyandjeffrey.net>. Distribute under the same terms as Perl itself.

Apache::SessionX extents Apache::Session. It was initialy written to use Apache::Session from inside of HTML::Embperl, but is seems to be usefull outside of Embperl as well, so here is it as standalone module. Apache::Session is a persistence framework which is particularly useful for tracking session data between httpd requests. Apache::Session is designed to work with Apache and mod_perl, but it should work under CGI and other web servers, and it also works outside of a web server altogether. Apache::Session consists of five components: the interface, the object store, the lock manager, the ID generator, and the serializer. The interface is defined in SessionX.pm, which is meant to be easily subclassed. The object store can be the filesystem, a Berkeley DB, a MySQL DB, an Oracle DB, or a Postgres DB. Locking is done by lock files, semaphores, or the locking capabilities of MySQL and Postgres. Serialization is done via Storable, and optionally ASCII-fied via MIME or pack(). ID numbers are generated via MD5. The reader is encouraged to extend these capabilities to meet his own requirements.

Apache::Singleton works the same as Class::Singleton, but with various object lifetime adapted for use under Apache.

Apache2::SiteControl is a set of perl object-oriented classes that implement a fine-grained security control system for a web-based application. The intent is to provide a clear, easy-to-integrate system that does not require the policies to be written into your application components. It attempts to separate the concerns of how to show and manipulate data from the concerns of who is allowed to view and manipulate data and why.

This is ApacheBench version 0.62, the Perl API for Apache benchmarking and regression testing. This project is meant to be the foundation of a complete benchmarking and regression testing suite for a transaction- processing mod_perl site. We needed to be able to stress our server to its limit while also having a way to verify the HTTP responses for correctness. We also extended the single-URL ab model to a multiple-URL sequence model. ApacheBench is based on the Apache 1.3.12 ab code (src/support/ab.c). Since the initial release, I have made efforts to merge in all the newest features of ab. Currently (v0.62) it has almost all the features of Apache 1.3.22 ab.