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.
