[TurboGears] Re: Identity Module Stability

[Jeff Watkins]

A visit represents a contiguous (or as nearly contiguous as we can get with the Web) session of interaction with your Web application. Pushing the expiry out indefinitely defeats this purpose. Other things may tie into the visit key like content popularity and it would be difficult to correlate if the visit lasted forever. Instead, how about serving an explicit cookie (tg_persistent_user?) that contains a key mapping the visitor to an identity record? You would probably want to put some safeguards in there via signing the cookie, but that's not particularly hard. On 3 May, 2006, at 12:15 am, Andrew Grover wrote: After investigating a little more, it looks like I should just bump the tg_visit expiry to way in the future, and problem solved with no further code needed :) -- Jeff Watkins http://newburyportion.com/ "Not everything that can be counted counts, and not everything that counts can be counted." -- Albert Einstein --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to turbogears@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---