On Wed, Jan 5, 2011 at 5:41 PM, Florian Apolloner <[email protected]>wrote:
> Hi, > > On Jan 6, 12:02 am, Russell Keith-Magee <[email protected]> > wrote: > > There are no backwards compatibility concerns here. We're talking > > about the class-based generic TemplateView. > > Sorry, I just noticed now, that the current function based views are > still function based and not wrappers around the class based views. > Then option (5) sounds great :) > > Cheers, Florian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<django-developers%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > My suggestion: Have cache_page return a wrapper around TemplateResponse, which overrides bake (or render or whatever we called it) to actually cache the rendered page, then when cache_page fetches something from the cache have just return the HttpResponse. Alex -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero "Code can always be simpler than you think, but never as simple as you want" -- Me -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
