On Wed, Aug 8, 2012 at 9:00 AM, Takashi Matsuo <[email protected]> wrote: > Hi prem, > > I would suggest setting appropriate cache timeout rather than trying > to control every edge-cache type things,
+1 to that. Can be useful to allow caching of html pages - help deal with traffic spikes, but set a shortish caching timeout (minutes, or at most hours), then use conditional-gets - either Last-Modified or Etag's, to allow the cache to continue to be used, but can be 'refreshed' as and when its later required. http://ruturajv.wordpress.com/2005/12/27/conditional-get-request/ (in the ultimate case, the user browser itself is a 'cache' - and there is no real way to "purge" that. Static assets (js/css etc) - is very easy to change the URL of the asset when it changes (the query string is one way of doing that). So for static assets setting a far future expire, and letting any cache tahts willing to store it do so, is almost certainly the best way. 'purging' is just changing the url. That can't be done for the html page itself as "cool urls never change" so, conditional gets (with some short term caching) is best. -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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/google-appengine?hl=en.
