Re: Pre-fetch rough draft

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
space.
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