Ok so using @cache.ram(...) def index(): return response.render(a=3)
caches the view and just serves it as html ? That is exactly what I want, thanks! -Thadeus On Fri, Oct 9, 2009 at 1:42 PM, mdipierro <mdipie...@cs.depaul.edu> wrote: > > No until you cache the view as well. > > Massimo > > On Oct 9, 12:35 pm, Thadeus Burgess <thade...@thadeusb.com> wrote: > > It also seems, when using cache on an action, that if I had set > > response.title = "About" within the function, it no longer gets set in > the > > cached version of the page. > > > > -Thadeus > > > > On Fri, Oct 9, 2009 at 11:00 AM, Thadeus Burgess <thade...@thadeusb.com > >wrote: > > > > > When you apply @cache to an controller action, what is actually cached, > is > > > it just the response from the function, or the generated html? or the > > > returned dict() ? > > > > > Is there a way to have web2py just cache the generated html and serve > it > > > like it was a static html file, depending on the request.env.path_info > ? > > > > > -Thadeus > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
