You can still use pyramid_beaker. It works fine under pyramid 1.5 . There are a few heated discussions in the archives over it. It's a sore point for many. I could be wrong on this, but last I checked it's not so much "deprecated" as it is "off the radar". A lot of us still use it for server side sessions. If it ever breaks there will be patches or a migration plan to something else.
One of the better candidates right now is pyramid_redis_sessions ; the only downside of it is that it only supports redis as a backend. for our needs, we needed a single package that could handle both a memcached/redis for production , but a pickled file storage for development. so we're still on beaker. On Tuesday, April 22, 2014 4:16:09 PM UTC-4, Anders Wegge wrote: > > As I read the documentation for SignedCookieSessionFactory, the data > stored in the session is not encrypted. So storing a CSRF token in the > session Cookie is not a good option. Pyramid_beaker seem to have been > deprecated with release 1.5, so which options are the best for a site with > very few actions requiring CSRF and other session data. My first thought is > to pickle the session data, and storing them in a blob in the user > database, but if there is something simpler and/or more elegangt available, > I'd like to hear the alternatives. > > > -- 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/d/optout.
