On 4/24/07, Damjan <[EMAIL PROTECTED]> wrote: > > You can store sessions (or the needed info) in just cookies, a > database (MySQL, Postgresql, etc) or memcached. It's not neccesseary > to store the session in files.
Agreed. memcached is very popular for scalable session servers, not just in the Pylons world. Cookies are a good option if you can keep the sessions really small. You may want to sign and/or encrypt them to prevent tampering. At my company, we're trying our hardest to simply not use sessions in order to avoid the problem. An ugly solution is to have your load balancer implement "session stickiness" so that you can use Pylons normal session mechanism. However, that's ugly because you can't just pull servers out of production anytime you want. This topic is covered very nicely in "Building Scalable Web Sites" and "Scalable Internet Architectures". Happy Hacking! -jj -- http://jjinux.blogspot.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
