Apache-SessionX
view release on metacpan or search on metacpan
Apache::SessionX - An extented persistence framework for session data
----------------------------------------------------------------------
Copyright (c) 1997-2001 Gerald Richter / ecos gmbh
You may distribute under the terms of either the GNU General Public
License or the Artistic License, as specified in the Perl README file.
THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTIBILITY AND FITNESS FOR A PARTICULAR PURPOSE.
$Id: README,v 1.2 2001/08/14 04:37:28 richter Exp $
OVERVIEW
========
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.
Addtionaly to Apache::Session, Apache::SessionX provides the following
possibilites:
- Configuration: Makefile.PL checks which componemnts are installed
on the system and interactivly builds a set of configuration,
SessionX.pm view on Meta::CPAN
1 ;
__END__
=head1 NAME
Apache::SessionX - An extented persistence framework for session data
=head1 SYNOPSIS
=head1 DESCRIPTION
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
( run in 2.446 seconds using v1.01-cache-2.11-cpan-e1769b4cff6 )