The name of the module implies that it provides Cookie based state preservation for the Session module.
For compatibility with previous versions, and also because it kinda makes sense, the default behavior is to set the cookie and the server side storage to expire at the same time. If the cookie has browser session based expiration then the data on the server might disappear before the ID in the client, which kinda sucks. The inverse is less annoying (stale data on the server) but might be a problem for high volume sites. On Thu, Jul 12, 2007 at 12:12:34 -0400, John Goulah wrote: > I am wondering why I have to explicitly set the config option > "cookie_expires" > to 0 to get a session cookie. You would think the module name implies that > by default its a session cookie, but it seems to set a timeout by default > and this must be overridden. > > > Thanks, > John > _______________________________________________ > 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/ -- Yuval Kogman <[EMAIL PROTECTED]> http://nothingmuch.woobling.org 0xEBD27418 _______________________________________________ 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/
