W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2012

Re: Pre-fetch rough draft

From: Yehuda Katz <wycats@gmail.com>
Date: Sat, 3 Nov 2012 16:10:20 -0600
Message-ID: <CAMFeDTUMFeDQUbdEof8+TQC-O0_WE6PTS4asg4aqyvJD0cGNeA@mail.gmail.com>
To: nop@yandex-team.ru
Cc: public-webapps WG <public-webapps@w3.org>, Mounir Lamouri <mounir@lamouri.fr>, Michael Nordman <michaeln@google.com>, chaals@myopera.com
Does this overlap with SPDY preloaded?

-- Yehuda Katz
(ph) 718.877.1325
On Nov 3, 2012 3:35 PM, <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.
> 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.
>
> --
> Sergey Nikitin
>
>
>
Received on Saturday, 3 November 2012 22:10:48 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:55 GMT