On Tue, Nov 17, 2009 at 3:02 PM, Peter Kasting <pkast...@google.com> wrote: > On Tue, Nov 17, 2009 at 3:00 PM, James Robinson <jam...@google.com> wrote: >> >> It seems like a browser will have to essentially stop rendering until >> it has finished downloading the entire .zip and examined it. > > I think mitigating this is why there are optional manifests. I agree that > if there's no manifest, this is really, really painful. I think manifests > should be made mandatory. > PK
Do you mean external manifests? Either way, the browser cannot start a download for any external resource until it downloads and parses out the manifest.txt for every resource bundle seen in the page so far. Whether it is pulling the manifest out of a .zip file or as a .txt by itself doesn't matter much, it's still an extra HTTP round-trip before any content can be downloaded (including content that is not bundled at all). - James _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
