Session Management?

[Z Monteca]

I just did an implementation of sessions. Personally I used
Apache::Session::File, but I see others have used CGI::Session. Does
anyone have any pros/cons they could lend on using this method/module for
management.

So far the one problem that I have run into is all the garbage clean I up
that has to be done. For every web request that is made it seems to create
a lot of unecessary session files in the session directory (after a few
hours I have upwards of 10's of thousands, but only have a few thousand
hits a day ~2,000). I am not sure why this is. A true con is that you have
to have run a cron script to clean up this directory every few hours. Is
this a standard element of using the Apache::Session::File module or is my
implementation seem to be messed up a bit?


-Z

 

[Malte Ubl]

I just did an implementation of sessions. Personally I used
Apache::Session::File, but I see others have used CGI::Session. Does
anyone have any pros/cons they could lend on using this method/module for
management.

So far the one problem that I have run into is all the garbage clean I up
that has to be done. For every web request that is made it seems to create
a lot of unecessary session files in the session directory (after a few
hours I have upwards of 10's of thousands, but only have a few thousand
hits a day ~2,000). I am not sure why this is. A true con is that you have
to have run a cron script to clean up this directory every few hours. Is
this a standard element of using the Apache::Session::File module or is my
implementation seem to be messed up a bit?

Apache::Session defines an interface to be extended with other backend
storage machanims. I like Apache::Session::CacheAny that uses the
Cache::Cache interface. This enables you to use in memory cache which
might be more appropriate for you.

malte

 

[Z Monteca]

Apache::Session defines an interface to be extended with other backend
storage machanims. I like Apache::Session::CacheAny that uses the
Cache::Cache interface. This enables you to use in memory cache which
might be more appropriate for you.

malte

This sounds much more appropriate. Session::File is horrible. I am going
to check out Session::CacheAny. Thanks for the insights.

-Z

 

[Z Monteca]

I have this problem with trying to implement Apache::Session::CacheAny.
Everytime I tie the session:

tie %session, 'Apache::Session::CacheAny', $id, {
CacheImpl => 'Cache::SizeAwareFileCache',
Namespace => 'bookstore',
DefaultExpiresIn => '12 hours',
AutoPurgeOnGet => 0,
AutoPurgeOnSet => 1,
MaxSize => 10_000,
};

no matter what I change the DefaultExpiresIn time to, my session variables
last max two minutes? Does anybody have any idea why this is happening?

Also, to use a persistent session, I would have to essentially tie %session
in every file where I want this session to exist, correct?

Thanks in advance.

-Z

 

[Malte Ubl]

no matter what I change the DefaultExpiresIn time to, my session variables
last max two minutes? Does anybody have any idea why this is happening?

No, I'm sorry

Also, to use a persistent session, I would have to essentially tie %session
in every file where I want this session to exist, correct?

I don't know what you are referring to. My projects usually only have a
single front end file, that instatiates the controller of the application.

The code that instantiates your session can be loaded in via require or
use just like any other code.

bye
malte