On Thu, Oct 15, 2009 at 9:09 PM, John Lorance <[email protected]> wrote: > Daniel, > I was basically using a version of what is described here. Tried this a > number of ways and basically, just found that this all works as long as you > don't call and methods that have this decorator. Just documenting this > here for future searches.
I had the same problem as in my application I fork a thread to handle batch processes like converting videos and generating PDF. Inside that thread I can't call any method with @beaker_cache decorator. After asking also in #pylons I ended up with creating an uncached version of the method (which is then called by the cached version) and use the uncached from the worker thread and the cached from the web application. That has been the only solution that I have been able to find, if someone knows how to correctly initialize pylons cache manager inside another thread or app I'm really looking to it :D --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
