W3C home > Mailing lists > Public > public-web-perf@w3.org > June 2014

cache hints and preresolutions

From: <bizzbyster@gmail.com>
Date: Mon, 23 Jun 2014 14:32:18 -0400
Message-Id: <BEC02A55-50AD-44F9-8B69-6FC8C1E32C85@gmail.com>
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Ilya,

Two additions to your doc: https://docs.google.com/document/d/1HeTVglnZHD_mGSaID1gUZPqLAa1lXWObV-Zkx6q_HF4/edit.

Cache hints:
We talked about the idea of supplying version information in preload (or subresource) hints via the sub-resource integrity attribute. But I'm not crazy about that idea b/c it means the browser needs to load an object from the browser disk cache and run a checksum on it in order to check whether or not that resource is the same as the one in the preload hint. Why not just allow us to specify cache version information via Last-Modified-Time and/or Etag? This makes it easy and fast to check to see if the cached version is current or not. Perhaps this could be a new attribute (version?) of the LINK header?

Preresolutions:
Also, it would be great if we could specify the result of DNS lookups and also inline HTTP responses. So, for instance, let's say I have a site called simple.html that has an iframe hosted by a third party site. That third party site includes a URL that always receives a 301 Permanent redirect. It'd be great if we could optimize the loading of the page by simply including that 301 response code and Location header in as a "preresolution" up front along with the other resource hints.

Thoughts? Anyone else?

Peter
Received on Monday, 23 June 2014 18:32:47 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:38 UTC