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

Re: [resource-hints] first spec draft

From: Nottingham, Mark <mnotting@akamai.com>
Date: Tue, 8 Jul 2014 22:08:16 -0500
To: Ilya Grigorik <igrigorik@google.com>
CC: public-web-perf <public-web-perf@w3.org>
Message-ID: <15C4A17C-3C79-4278-93E4-32B8AC8EE7AC@akamai.com>
Hey Ilya,

Had a quick look, like it so far.

A couple of nits:

1) The name is really generic. Something more decriptive would be better, e.g., "Link Relations for Browser Performance" (yes, I know that's not as catchy)

2) The "Caching Grace Period" section seems a bit iffy to me... I wouldn't express this as being an override of the caching policy, but rather of it being applied *after* the cache; i.e. the rendering engine itself effectively caches it for next use.

3) Those link relations will need to be registered...

On 9 Jul 2014, at 3:35 am, Ilya Grigorik <igrigorik@google.com> wrote:

> First run at the spec based on previous discussions [1] and feedback:
> https://igrigorik.github.io/resource-hints/
> "This specification defines preconnect, preload, prefetch, and prerender hints that the developer, or the server generating or delivering the resources, can use in an interoperable way to assist the user agent in the decision process of which origins it should connect to, which resources it should fetch to improve performance, and which resources may be required by the next navigation."
> Feedback, nitpicks, etc., all welcome!
> ig
> [1] https://docs.google.com/document/d/1HeTVglnZHD_mGSaID1gUZPqLAa1lXWObV-Zkx6q_HF4/edit#

Mark Nottingham    mnot@akamai.com    https://www.mnot.net/
Received on Wednesday, 9 July 2014 03:08:45 UTC

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