I have a third addition that I forget to mention: expected object size.
Often the server will know the expected size of a sub-resource. This size helps the browser to fetch the object optimally as it allows the browser to figure out how to assign requests across a pool of TCP connections given the state of those connections. So, for instance, if I have to download 4 objects and I know their sizes -- the first three are 1.5 KB and the fourth is 4.5 KB. Then I can request the first three over one HTTP/2 connection to a server with an initcwnd of 3 and the fourth over a second HTTP/2 connection of initcwnd 3. This allows me to fetch all four resources in a single round trip.
Intelligent use of expected file sizes to optimize the use of TCP connection pools has a huge performance benefit for fetching a large number of small objects.
Do you agree this type of information can be included in sub-resource hints?
Thanks,
Peter
On Jun 23, 2014, at 2:32 PM, bizzbyster@gmail.com wrote:
> Ilya,
>
> Two additions to your doc: Received on Wednesday, 25 June 2014 13:58:47 UTC