Let me clarify that using memcached in beaker doesn't work ONLY FOR STORING SESSIONS.
It does work for regular caching in beaker (e.g. using @beaker_cache decorator to cache controller actions etc). This is not a bug, it's basically an incorrect implementation, which uses wrong design and is completely untested. For storing sessions in mecached you need to do the same thing as when storing session in a file - pickle the session and store it as a single key in memcached. So you can update or remove the session object in a single mecached call, and all the sessions attributes will have the same expiration. Storing each session attribute as a separate record is incorrect because memcached doesn't allow you to update/iterate/delete groups of records together. On Dec 30, 2:51 pm, "Mike Orr" <[email protected]> wrote: > On Tue, Dec 30, 2008 at 1:10 PM, Tycon <[email protected]> wrote: > > > So I guess no one is actually using memcached for storing sessions ? > > Or of you do, do you define your own memcached interface instead of > > the > > Beaker memcached interface for session storage ? > > I haven't use memcached, and I doubt many Pylons applications do. > Some of the problems you're describing look like they may be Beaker > bugs, but I think Ben is the only one who knows enough about Beaker's > internals to evaluate that. > > -- > 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 -~----------~----~----~----~------~----~------~--~---
