@cache.action(....public=False) will cache the content server-side and send along "in the past" cache headers, marking also the content as private, so browsers are forced to reissue the request for that page.
On Tuesday, March 18, 2014 5:16:24 PM UTC+1, Anthony wrote: > > 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. >> > > Well, you're already using cache() within the index function itself -- it > will be no different to use the decorator instead. The main issue is to > make sure the key is unique to the specific content being cached (e.g., if > there is a query string in the URL that affects the returned response, make > sure that is part of the key). > > 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.
