- From: Ilya Grigorik <igrigorik@google.com>
- Date: Mon, 28 Jul 2014 09:30:54 -0700
- To: David Lerner <davidflerner@gmail.com>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Monday, 28 July 2014 16:32:01 UTC
On Fri, Jul 25, 2014 at 9:56 AM, David Lerner <davidflerner@gmail.com> wrote: > One topic that was also discussed was cookie handling, and the potential > for adding hint information that indicates whether the cookies are > consequential as a way to determine whether an object that is fetched via > the hint can be used later. If the request is initiated due to a hint, the UA will process it using all the same logic, which includes appending the appropriate cookies, applying appropriate security policies, and so on. If the concern is that you must first execute JS to manipulate/update your cookies before the request goes out, then you already have to hide your resources from the doc parser + preloader (which creates its own set of performance problems), but you can still inject the hints dynamically via JS: https://igrigorik.github.io/resource-hints/#dynamic-scheduling ig
Received on Monday, 28 July 2014 16:32:01 UTC