I see you point, and I also tried experimenting with "extend_session_expires". However it did not seem to help. Did you manage to get it to replace the cookies in the client ?
In ether case - auto-extending the session is only good as long as the client keeps accessing your server. Sometime, sooner or later the session will expire (and for security reasons you probably will not want to extend the session then). My workaround is actually a handler for a situation when a session is totally expired, with a few lines added to kill the old session. P.S.: The relevant part of my project had to rely on $c->session, rather then $c->user objects. Somehow $c->user -based code handles session expiry much better. On 3/29/07, Dmitry <[EMAIL PROTECTED]> wrote:
VT> My workaround will: VT> 1) Delete the old session VT> 2) Create a new session VT> 3) Return a dummy page, along with a new cookie and a redirect to VT> site's main page There is easier workaround - just call $c->reset_session_expires on login. Why nor reset_session_expires neither extend_session_expires are not documented if they are public? _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
_______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
