On Sun, Feb 16, 2014 at 12:36:51PM -0600, Theron Luhn wrote: > Thanks for letting me know. I'll look into pyramid_redis_sessions.
Not meaning to fan a smoldering thread here, but, if cookie-based session storage (where all the data goes in the cookie and there is no server-side storage of session data) will work in your use case, that is probably the most painless way to go. Pyramid provides for cookie-based session storage natively. Pyramid 1.5 provides SignedCookieSessionFactory for this. http://docs.pylonsproject.org/projects/pyramid/en/1.5-branch/narr/sessions.html Older pyramids provide UnencryptedCookieSessionFactoryConfig: http://docs.pylonsproject.org/projects/pyramid/en/1.4-branch/narr/sessions.html No redis required. When your server fails-over, not only will there (hopefully) be no exceptions thrown, but there will be no session data lost, since its all stored client-side. More context here: https://groups.google.com/forum/#!searchin/pylons-discuss/session|sort:date/pylons-discuss/RQjev5QXBqc/Xf1pUHXl1-0J Jeff -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/groups/opt_out.
