On Wed, Dec 16, 2009 at 9:01 PM, Ales Zoulek <ales.zou...@gmail.com> wrote: > Obviously you need to pickle the whole generated data, not just generators. > 1] But I'd use response.content propery that returns the string no matter > how the request is created. > 2] Subclassing the cache middleware, or creating your own decorator for that > seems like a cleaner way then pathing the original django sources :) > > Regards, > A
The entire point of using a generator driven response is to avoid blocking until the entire response is generated, so going through the response.content property would not be useful. Now that I've actually implemented this, hopefully it can be adjusted/improved and be added back to django. For the drop in solution (ie, sitting in an app, outside of django code), I had to reimplement the cache_page decorator, and the middleware classes UpdateCacheMiddleware and CacheMiddleware, but the only changes are really to UpdateCacheMiddleware, the other classes/functions are mainly copy/pastes of their originals, with minor tweaks to use the improved UpdateCacheMiddleware. It still surprises me that the django supplied @cache_page decorator doesn't work with django supplied response objects (and doesn't document that fact either). Cheers Tom -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
