Difference between revisions of "Design Specs: Session Cleanup"
From WormBaseWiki
Jump to navigationJump to searchLine 16: | Line 16: | ||
=session cleanup= | =session cleanup= | ||
+ | |||
+ | browser session will expire after 3600 second as set in the config. | ||
+ | logged in user session does not expire | ||
use Catalyst::Plugin::Scheduler to clean up expired sessions in a cron-like fashion | use Catalyst::Plugin::Scheduler to clean up expired sessions in a cron-like fashion | ||
+ | <pre> | ||
+ | __PACKAGE__->config->{schedule}={ | ||
+ | at => '40 10 * * *', | ||
+ | event => '/cron/remove_sessions', | ||
+ | } | ||
+ | </pre> |
Revision as of 15:42, 31 January 2011
session storage
Session::Store::DBI
__PACKAGE__->config->{'Plugin::Session'} = { expires => 3600, dbi_dbh => 'Schema', dbi_table => 'sessions', dbi_id_field => 'id', dbi_data_field => 'session_data', dbi_expires_field => 'expires', };
note: Catalyst::Plugin::Session::Store::DBIC does not compatible with Session::PerUser plugin.
session cleanup
browser session will expire after 3600 second as set in the config. logged in user session does not expire
use Catalyst::Plugin::Scheduler to clean up expired sessions in a cron-like fashion
__PACKAGE__->config->{schedule}={ at => '40 10 * * *', event => '/cron/remove_sessions', }