On Oct 10, 2005, at 5:25 PM, Cees Hek wrote:
Although that works, I am not sure if that is the cleanest way of
doing it. I would stick with just STORE => 'Session' there, and
move the CGI::Session->name('Fox') call below
Ok, I moved it and it works, and it makes more sense too.
Also, is there a reason why you set the session expiry to 1 week, but the cookie expiry to 1 month? If you leave off the cookie expiry, then CAP::Session will automatically set the expiry on the cookie to the expiry of the Session object.
Well, sort of. I want to test how the app maintains state when the users session expires so I've been playing with those values. The cookie was set to expire in one minute, the session was set to expire in one week. In my real world app I want to make the user login if they've been away from their screen for one hour, but allow them to continue working where they left off. I'm not sure where I read that this was possible, (I've been reading a lot lately) but I'm at the point where I'd like to implement it in my test app.
Thanks again, Cees.
--
Bill Stephenson
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/suppressed/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.