Summary: | implement Link: header | ||
---|---|---|---|
Product: | WebKit | Reporter: | Gavin Peters <gavinp> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | UNCONFIRMED --- | ||
Severity: | Normal | CC: | abarth, ap, front.end.developing, gavinp, jerome, mathias, me, miket, mike, nickshanks |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | PC | ||
OS: | OS X 10.5 | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=194539 | ||
Bug Depends on: | 102936, 51941, 57842 | ||
Bug Blocks: | 20018 |
Description
Gavin Peters
2011-01-05 11:43:52 PST
I'm wondering what the difference between link=prefetch and link=subresource is. I couldn't find the latter documented anywhere. Is this the same as prefetch, but delaying load event? > I'm wondering what the difference between link=prefetch and link=subresource is. I couldn't find the latter documented anywhere.
I believe prefetch is a low priority load (so it waits until all the other resources for the page are loaded before clogging up the network) whereas subresource is a high priority load that tries to load the resource in time before its needed by the same page.
To be clear about my first comment, I think the initial implementation of the Link header should shy away from rel types that mutate or affect data; so let's stick with rel=prefetch, rel=subresource, rel=dns-prefetch and possibly rel=icon. Test cases: http://greenbytes.de/tech/tc/httplink/ What is the state of this bug? We have implemented Link header for mobile and I was disappoint why nobody implement it well. |