* On Sat, Mar 01 2008, Bill Moseley wrote:
> Is it expected that the application update the session every request
> to prevent expiry while a user is actively using the application?
Is the problem that $c->session->{__expires} doesn't get updated, or is
the problem that the Cache backend is losing things due to its expiry
not being updated?
In the second case, it's just a bug in the Session::Store::Cache store
that can be fixed with the addition of a backend_expires configuration
key, probably set to "never" by default. It's annoying to have two
expiration times, but that can be easily worked around. (Set cache
expiration every time you update __expires, or just set it to 2038 and
hope Catalyst expires it for you.)
Regards,
Jonathan Rockway
_______________________________________________
List: [email protected]
Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/[email protected]/
Dev site: http://dev.catalyst.perl.org/
