On Sun, Jun 29, 2008 at 3:30 PM, Jonathan Vanasco <[EMAIL PROTECTED]> wrote: > > I don't really understand what you're saying... but from what I think > you're trying to suggest, I'd have to disagree with this concept. > > Sessions simply allow information to persist between requests. Going > into sessions and mangling them outside of the request is a very > unique requirement that is often wholly unnecessary - and bad design. > > Walking through the entirety of sessions means analyzing and updating > each one - including those that are dead / old / timed out.
Yet it's necessary for precisely that reason -- to delete old sessions. But there's no reason not to make it a general API for statistics and the like, or an admin screen for debugging. Beaker may have an "iterate sessions" method somewhere. -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
