On Wed, Jun 25, 2008 at 10:22 AM, Ben Bangert <[EMAIL PROTECTED]> wrote: > 2) Use cookie-based sessions, to avoid hitting the filesystem loading > session data. You'll still need to hit the database on occasion to ensure > the user is logged in, but this can avoid the file-system hit as well.
Er, as long as you aren't storing info in the sessions you don't want the user to see. This works normally because only the session ID is exposed to the user, but would break with cookie-based sessions. I think there's also a small limit on cookie size, which would suck if you're storing largish data structures in the session. -- 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 -~----------~----~----~----~------~----~------~--~---
