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

Re: Pre-fetch rough draft

From: Yuval Sadan <sadan.yuval@gmail.com>
Date: Tue, 30 Oct 2012 12:44:35 +0200
Message-ID: <CAJaqjSq3k569pfoJX4HXUP6c+XO4rTgF7=MM+EVTyN=ChEbLDQ@mail.gmail.com>
To: Charles McCathieNevile <chaals@myopera.com>
Cc: public-webapps WG <public-webapps@w3.org>
Adding another "well-known location" may cause (yet another) 404 error for
sites lacking this file, similar to favicon.ico. Plus it takes up URL
I suggest that if such a file is used, it should not be in a "well-known
location" but a site specific location that can be specified by an HTTP
header and/or <meta/> tags.

On Tue, Oct 30, 2012 at 11:22 AM, Charles McCathieNevile <chaals@myopera.com
> 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.
> cheers
> --
> Charles McCathie Nevile - private mail account
Received on Tuesday, 30 October 2012 10:45:37 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:49 UTC