On 8/25/07, Ben Bangert <[EMAIL PROTECTED]> wrote: > > I'd highly suggest memcached rather than database backend. It's easy > to setup, and of course, very fast. :)
Yes, but as far as I know, memcached objects can be always replaced, that is, you cannot define an object to be persistent, can you? Thus, one also needs to back up the session data to a persistent storage so it does not get replaced when the cache fills up. Here's the setup info for memcached: > > beaker.session.type = ext:memcached > beaker.session.url = 192.147.32.2 > > The url can be a comma separated list of IP/hostnames as well should > you be using multiple memcached servers. Thank you. This helps, but still, I need to define the persistent storage in addition to the memcached due to above mentioned reason. -- --PJ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
