- From: Michael Nordman <michaeln@google.com>
- Date: Tue, 30 Oct 2012 15:26:13 -0700
- To: Mounir Lamouri <mounir@lamouri.fr>
- Cc: public-webapps WG <public-webapps@w3.org>, chaals@myopera.com
Received on Tuesday, 30 October 2012 22:26:41 UTC
The appcache is encumbered with guarantees about atomically updating a set of resources and then explicitly not hitting the network for them once up to date to ensure the site/app will function if the network really is complete gone. This gist of this prefetch list seems different. More of a hint to warm things up if possible and viola things are more responsive if those hints are taken. On Tue, Oct 30, 2012 at 2:58 PM, Mounir Lamouri <mounir@lamouri.fr> wrote: > On 10/30/2012 10:22 AM, Charles McCathieNevile wrote: > > Hi, > > > > I mentioned this and it's somethign we are working on. > > > > Basic idea: site provides list of resources that it uses and can be > > cached for general improvements on the whole site. (We're seeing > > load-time improvement from 50% - 300% in our testing. We are using it on > > sites - mail.yandex.ru/prefetch.txt has an example). > > > > The draft "spec" here is still very rough, but it shows what we've > > implemented and some of what we think it is good for. > > > > This is meant as input to the appcache/packaging/etc discussion, and may > > or may not be something this group takes on. > > At a first glance, it seems that appcache could do the same things. > Which use cases appcache can't currently solve? In the process of fixing > appcache, it could be interesting to add those use cases. > > -- > Mounir > >
Received on Tuesday, 30 October 2012 22:26:41 UTC