On Thu, Dec 17, 2009 at 7:58 AM, Ales Zoulek <ales.zou...@gmail.com> wrote:
> > 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. >> >> > Using your patch the respose will be blocking as well. The block wil just > happen a bit later in middleware processing. > > > >> 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). >> >> > That's true. Try creating a ticket for it. > > Please don't. There is already a ticket covering issues with generators in responses: http://code.djangoproject.com/ticket/6527 Karen -- 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.
