On Aug 29, 2007, at 3:56 PM, Robert Ian Smit wrote:
Yes. I suppose that the problem was the cut off issue. I am not actually caching the html body. I am storing the entire response object like beaker_cache does. A Response object whose pickled representation is truncated can not be restored to its original form and is deemed to be insecure by the unpickling code.I don't know whether a lot of people are using beaker.ext.database. There are not a lot of docs and a lockfile is still required (not sure why), but it works for me as an easy to implement and more importantly completely tranparent caching mechanism.
The lockfile is to restrict how many processes/threads may decide to refresh the cache at once. Ie. if multiple Python processes decide a cache needs to be refreshed and its already being refreshed, they need a way to know that one of them is already doing it, thus the lockfile.
Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature
