Re: mod_perl session beans

The obvious problem with caching things in memory in mod_perl is that every Apache process has its own Perl interpreter , that they do not share (read-write) memory, and that you have no control over which process handles which request. All this makes in-memory session tracking a little difficult.

You could have a look into using shared memory, for example with Apache::Session::SharedMem.

Maybe this has changed in mod_perl2.

Comment on Re: mod_perl session beans

Replies are listed 'Best First'.
Re^2: mod_perl session beans by hakkr (Chaplain) on Jan 10, 2005 at 15:51 UTC
Hi, Yes the only problem with shared memory variable is they have to be read only or they wont stay shared. Shame Apache::Session::SharedMem is not production ready, maybe it will make a good starting point anyway thanks	[reply]
Re^3: mod_perl session beans by perrin (Chancellor) on Jan 12, 2005 at 17:02 UTC
I expect Apache::Session::SharedMem to be very slow, since it is built on the very slow IPC::Cache module. The caching modules I mentioned below are at least ten times as fast.	[reply]