It has been mentioned that using dogpile.cache for sessions doesn’t make much sense, see this comment by zzzeek: http://techspot.zzzeek.org/2012/04/19/using-beaker-for-caching-why-you-ll-want-to-switch-to-dogpile.cache/#comment-532502543
Use a signed/encrypted cookie to have the session store off-loaded to the client, or store the data into a database and use it WITH dogpile.cache to provide caching as appropriate (sqlalchemy with dogpile.cache for example), and return a cookie that contains a unique ID that associates it with the database data. If you need server side sessions (and I would take some time figuring out why you need them) take a look at pyramid_redis_sessions for example. Bert On Dec 12, 2013, at 10:14, Jonathan Vanasco <[email protected]> wrote: > It's still maintained for bug-fixes [ https://github.com/bbangert/beaker ] > > it's "feature complete" and they've been accepting security patches [ > https://github.com/bbangert/beaker/pulls?direction=desc&page=1&sort=created&state=closed > ] > > now i remember why I kept putting this on the backburner -- creating a > pyramid_dogpile package would require creating some session management to > store onto dogpile , and figuring out how to get pyramid's sessions and > dogpile to work nicely. i didn't know the internals of either well enough to > try that. > > I think the big problem with beaker is that it does too much , and needs > multiple projects to replace it. > > dogpile just handles the caching mechanism into a datastore. > > beaker offers: > > caching middleware > sessions > -- cookie based > -- misc backend based > - other stuff i can't remember > > dogpile fixes & replaces a large amount of the beaker internals , but doesn't > have the middleware or sessions. > > > > > On Wednesday, December 11, 2013 11:15:05 PM UTC-5, Mike Orr wrote: > Yes but if Beaker is unmaintained it raises questions about using it > in production, especially over the longer term. I also have four > Pylons sites that are using Beaker, which will be harder to convert to > something else. (Although one of them will be upgraded to Pyramid in > January, and another by June.) > > > > -- > 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. -- 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.
