- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Mon, 05 Nov 2012 13:28:43 +0100
- To: nop@yandex-team.ru
- CC: Michael Nordman <michaeln@google.com>, Mounir Lamouri <mounir@lamouri.fr>, public-webapps WG <public-webapps@w3.org>, chaals@myopera.com
On 2012-11-02 11:16, nop@yandex-team.ru wrote: >> On Tue, 30 Oct 2012, Michael Nordman <michaeln@google.com> wrote >> >> 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. >> > > Yes. Exactly. > It's not about offline apps, it's about reducing loading time. There's already the "prefetch" link relation that you could use. > Prefetch manifest is a way to tell browser what should be downloaded in advance. > So when user opens the site (for the first time) all resources (css/js/images/...) are already cached. > > And if later site's resources are updated browser could check prefest manifest and > re-download all new resources in background. Before user visited site again. But then you don't need a manifest for that (see above). Best regards, Julian
Received on Monday, 5 November 2012 12:29:14 UTC