Perrin Harkins wrote:
> Brian Parker wrote:
> > I'm trying to use Apache::Session::MySQL. Since I'm generating my own
> > session key outside of Apache::Session (using $ENV{REMOTE_USER}), what
> > method(s) do I have to override to prevent Apache::Session from trying
> > to create a session key for me? Since I'm not using Apache::Session's
> > key generation capability, is there another implementation that would be
> > more appropriate for my application?
>
> Just write a replacement for Apache::Session::Generate::MD5.
Thanks Perrin. That at least got me looking in the right place.
I had to replace 'Apache::Session::Generate::MD5' as you suggested and then
create my own subclass of 'Apache::Session' (specifies which 'validate' and
'generate' subroutines to call). Because 'Apache::Session' does not provide a
way to create a session with a certain id, I ended up having to do doing
something like this:
my $rm = $ENV{REMOTE_USER}
eval{
# see if the user has a session created
tie %session, 'WC::ApacheSession::MySQL', $rm, {
Handle => $dbh,
LockHandle => $dbh
};
1;
} or do {
# create the session using $ENV{REMOTE_USER} as key
tie %session, 'WC::ApacheSession::MySQL', undef, {
Handle => $dbh,
LockHandle => $dbh
};
};
... to handle the case of the the first time a user. This will work until I
invent a cleaner solution.
regards,
Brian
> You can
> look at Apache::Session::Generate::ModUsertrack, which is probably very
> close to what you want to do.
>
> - Perrin
