Re: Packaging on the Web

Alex,

> > Does having a simple textual manifest file that just lists the content of
> > the package as the first item in the package help at all?
>  
> Unclear. It's a foot-race, after all. A client will do request to get the
> document, which usually streams in pretty quickly relative to the RTT's you
> need to navigate for sub-resources. This is confounded by advice like this
> which indicates to authors that they should be requesting some resources as
> early as possible in their documents:
>  
> https://developers.google.com/speed/docs/best-practices/rtt#PutStylesBeforeScripts  
>  
> This is especially important for resources that are going to be fetched
> off-origin and for which warming up DNS can add considerable latency.

Just to note that packages won’t contain off-origin resources, so it’s still perfectly reasonable for publishers/browsers to do that. Not that I think it affects the majority of your argument.

Jeni
--  
Jeni Tennison
http://www.jenitennison.com/

Received on Thursday, 6 February 2014 09:16:49 UTC