Apache-SessionX
view release on metacpan or search on metacpan
SessionX.pm view on Meta::CPAN
sub validate {
#This routine checks to ensure that the session ID is in the form
#we expect. This must be called before we start diddling around
#in the database or the disk.
my $session = shift;
if ($session->{data}->{_session_id} !~ /^[a-fA-F0-9]+$/) {
die 'Invalid session id' ;
}
}
#
# For Apache::Session >= 1.50
#
sub populate
{
my $self = shift;
my $store = $self->{args}->{Store};
my $lock = $self->{args}->{Lock};
if (!$self->{populated})
{
my $gen = $self->{args}->{Generate};
my $ser = $self->{args}->{Serialize};
$self->{object_store} = new $store $self if ($store) ;
$self->{lock_manager} = new $lock $self if ($lock);
$self->{generate} = \&{$gen . '::generate'} if ($gen);
$self->{'validate'} = \&{$gen . '::validate'} if ($gen && defined (&{$gen . '::validate'}));
$self->{serialize} = \&{$ser . '::serialize'} if ($ser);
$self->{unserialize} = \&{$ser . '::unserialize'} if ($ser) ;
if (!defined ($self->{'validate'}))
{
$self->{'validate'} = \&validate ;
}
$self->{populated} = 1 ;
}
else
{ # recreate only store & lock classes as far as necessary
$self->{object_store} ||= new $store $self if ($store) ;
$self->{lock_manager} ||= new $lock $self if ($lock);
}
return $self;
}
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
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.
=head1 INTERFACE
The interface to Apache::SessionX is very simple: tie a hash to the
desired class and use the hash as normal. The constructor takes two
optional arguments. The first argument is the desired session ID
number, or undef for a new session. The second argument is a hash
of options that will be passed to the object store and locker classes.
=head2 Addtional Attributes for TIE
=over 4
=item lazy
By Specifing this attribute, you tell Apache::Session to not do any
access to the object store, until the first read or write access to
the tied hash. Otherwise the B<tie> function will make sure the hash
exist or creates a new one.
=item create_unknown
Setting this to one causes Apache::Session to create a new session
with the given id (or a new id, depending on C<recreate_id>)
when the specified session id does not exists. Otherwise it will die.
=item recreate_id
Setting this to one causes Apache::Session to create a new session id
when the specified session id does not exists.
=item idfrom
instead of passing in a session id, you can pass in a string, from which
Apache::SessionX generates the id in case it needs one. The main advantage
from generating the id by yourself is, that in 'lazy' mode the
id is only generated when the session is accessed.
=item newid
Setting this to one will cause Apache::SessionX to generate a new id every
time the session is saved. If you call C<getid> or C<getids> it will return
the new id that will be used to save the data.
=item config
( run in 1.333 second using v1.01-cache-2.11-cpan-e1769b4cff6 )