El martes, 18 de marzo de 2014 12:16:45 UTC-3, Anthony escribió: > > - A "layout.html" containing user's navbar and site's header and footer. >> - An "index.html" that extends layout.html >> - An "content.html" that **doesn't** extends layout.html >> - An index() controller function that **doesn't** use @cache.action >> decorator. Instead, the function uses response.render() specifying >> "content.html" as the view file to be rendered, and stores the results of >> the rendering in the cache. That result is passed as a variable to >> "index.html" view. >> > > Seems like a reasonable approach. If you don't want to cache within the > index function, you could instead use the @cache() decorator (rather than > @cache.action). >
I will give it a try. I haven't tried that because the book suggested using @cache.action, but I will give it a try. > > Feel free to open a Google Code issue about not being able to turn off > client side caching with @cache.action. That should be allowed, and this is > a good use case for it (i.e., the need to cache only the output of the > function, but not the entire rendered HTML due to user-specific data on > each page). > I'll do it today, thanks again for the help! Regards, Lisandro. > Anthony > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
