Hi,
>
> I've recently started using Embperl/mod_perl developing a front-end to a
> database system and for a while everything seemed to be working really
> well, however, now I'm stuck because the session management fails for
> either one part of the program or another depending on how I configure
> things.
>
> Originally I didn't do any special session configuration, I just started
> using Embperl's %udat with what appeared to be success: most of the time
> my session data was there and seemed to work fine. I realise now that
> this was probably to do with the way mod_perl handles things and not
> really what I was actually after.
>
> I've tried setting up the DBIStore method but then the program fails to
> run completely with error messages from DBIStore.pm. I then switched
> and tried the FileStore method which worked with just about everything
> except it kept losing my DBI statement handles between accesses.
You _cannot_ store DBI handles in either a File or a Database!!!
> I then
> switched to MemoryStore which kept my DBI handles ok but loses other
> session data that I'm trying to maintain. This is really frustrating
> since I don't really understand how two different backend storage class
> could lose/keep different things!
>
MemorySTore works only for threaded environemt. On Unix every Child has it's
own process menory, so MemorySTore is useless on Unix
So use FileStore or DBISTore, but don't try to store any sort of handle.
That can't work, because a handle is bould to a child process and is useless
in another Apache child, which may serve the next request of the same user
Gerald
