+1 to breaking the dependency between fetching the resource and how it is later
used in the document. This type of “late binding” enables many page
optimizations.
Peter
PS. My apologies if you’ve already seen a message saying similar. I’m not sure
if the mailing list is accepting my messages o
We need to bite the bullet and add a priority attribute and an expected-size
attribute.
Priority:
The web server will often have information that allows it to know better than
the UA about the priority of objects. Basing this on type is not super useful
when we have only a few types and we ha
https://docs.google.com/document/d/1jSpWc6jkrUoYtGWcxev9Blkkv9RhoO1XtqinBvXqhgY/edit
Would suffice for priority.
Peter
On Aug 29, 2014, at 9:59 AM, bizzbys...@gmail.com wrote:
> We need to bite the bullet and add a priority attribute and an expected-size
> attribute.
>
> Priority:
> The web
Different aspects of priority are expressed in some of Ian’s loadpolicy
attributes (block, async, optimistic, low-priority). Currently web browsers use
the type of loadable element to determine priority. In Ilya’s proposal this can
be found in the “as” attribute in the case of LINK rel=preload.
that waterfall charts can visualize preload
“hits”, meaning preloaded resources that are used by the browser.
https://github.com/bizzbyster/ResourceHintsDocs/blob/master/Preload_Used_Waterfall.adoc
Let me know if anyone has any comments,
Thanks,
Peter
