Just to follow up, my problem with Beaker disk-based sessions On Sat, Mar 14, 2009 at 1:24 PM, Michael Bayer <[email protected]> wrote: > > I'd consider memcached sessions since they don't rely on file locks. > > > > On Mar 13, 2009, at 3:31 PM, Mike Orr <[email protected]> wrote: > >> >> ---------- Forwarded message ---------- >> From: Michael Bayer <[email protected]> >> Date: Wed, Mar 11, 2009 at 11:05 AM >> Subject: Re: Beaker error >> To: [email protected] >> >> >> >> Mike Orr wrote: >>> >>>> This site gets the most load, at 1.1 million hits/month. The >>>> next-highest site is 228,000. They all have been using Beaker >>>> sessions without a problem, until I put session.id in the base >>>> controller and then this site started giving errors. >>
Just to follow up, my session problems disappeared. I'm not sure whether it was reinstalling Beaker, or having forgotten to restart the site after moving it to a new virtualenv. But in any case, it's running now on Beaker 1.2.3. I'm still using disk-based sessions. The memcache backend was underdocumented, the cookie backend would have required significant changes to my code to use shorter session values, SQLite gave "disk image corruption" errors because it didn't like the threading, and MySQL just had an ordinary permission error I could have fixed if I'd been more persistent. One issue in Beaker is there are two SQLAlchemy backends in the code but only one of them works. I think it's the one that's not in the documentation, but I've deleted my INI file already so I'm not sure which one worked. -- 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 -~----------~----~----~----~------~----~------~--~---
