On 2012-11-08 17:31, Sergey Nikitin wrote:
...
Maybe you never visited the page or your cookies are expired (or you logged
out).
And visiting any page (with all cookies/other headers) is irreversible action.
It affects statistics, it could do something without your knowledge (marking
message
On 04.11.2012, at 2:10, Yehuda Katz wrote:
> Does this overlap with SPDY preloaded?
>
I can't find anything about "SPDY preloaded".
Is it server push and server hint
http://www.chromium.org/spdy/link-headers-and-server-hint
?
--
Sergey Nikitin
On 06.11.2012, at 12:49, Julian Reschke wrote:
> On 2012-11-06 09:28, Sergey Nikitin wrote:
>>
>> On 05.11.2012, at 16:28, Julian Reschke wrote:
>>
Yes. Exactly.
It's not about offline apps, it's about reducing loading time.
>>>
>>> There's already the "prefetch" link relation
On 2012-11-06 09:28, Sergey Nikitin wrote:
On 05.11.2012, at 16:28, Julian Reschke wrote:
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.
You need at least two pages to start prefetching.
Why
On 05.11.2012, at 16:28, Julian Reschke wrote:
>>
>> 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.
>
You need at least two pages to start prefetching.
And you can't prefetch anything for the
On Tue, 30 Oct 2012 10:22:47 +0100, Charles McCathieNevile
wrote:
Hi,
I mentioned this and it's something 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
On Mon, 05 Nov 2012 13:28:43 +0100, Julian Reschke
wrote:
On 2012-11-02 11:16, n...@yandex-team.ru wrote:
On Tue, 30 Oct 2012, Michael Nordman wrote
The appcache is encumbered with guarantees about atomically updating a
set of resources and then explicitly not hitting the network for the
On 2012-11-02 11:16, n...@yandex-team.ru wrote:
On Tue, 30 Oct 2012, Michael Nordman 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 net
Does this overlap with SPDY preloaded?
-- Yehuda Katz
(ph) 718.877.1325
On Nov 3, 2012 3:35 PM, wrote:
> > On Tue, 30 Oct 2012, Michael Nordman wrote
> >
> > The appcache is encumbered with guarantees about atomically updating a
> set
> > of resources and then explicitly not hitting the network
> On Tue, 30 Oct 2012, Michael Nordman 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
On Oct 30, 2012, at 11:19 AM, Julian Reschke wrote:
> On 2012-10-30 10:57, Anne van Kesteren wrote:
>> On Tue, Oct 30, 2012 at 10:46 AM, Florian Bösch wrote:
>>> The specification states that "Prefetch requests must not include
>>> cookies." which is not an effective measure to prevent user prof
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
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%
On 2012-10-30 11:44, Yuval Sadan wrote:
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 lo
On 2012-10-30 11:31, Brady Eidson wrote:
On Oct 30, 2012, at 11:19 AM, Julian Reschke wrote:
On 2012-10-30 10:57, Anne van Kesteren wrote:
On Tue, Oct 30, 2012 at 10:46 AM, Florian Bösch wrote:
The specification states that "Prefetch requests must not include
cookies." which is not an effe
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
he
On 2012-10-30 10:57, Anne van Kesteren wrote:
On Tue, Oct 30, 2012 at 10:46 AM, Florian Bösch wrote:
The specification states that "Prefetch requests must not include
cookies." which is not an effective measure to prevent user profiling.
I suspect it's to reduce the size of the request.
->
It's also a little unclear to me how prefetch improves the html
manifest or how they compare. It seems as if prefetch does pretty much
the same as the manifest except that it distributes fetching of the
actual resources out over time that the user might not be visiting a
site. Wouldn't it make more
On 2012-10-30 10:22, 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
On Tue, Oct 30, 2012 at 10:46 AM, Florian Bösch wrote:
> The specification states that "Prefetch requests must not include
> cookies." which is not an effective measure to prevent user profiling.
I suspect it's to reduce the size of the request.
--
http://annevankesteren.nl/
The specification states that "Prefetch requests must not include
cookies." which is not an effective measure to prevent user profiling.
For instance somebody could auto generate the prefetch.txt tailored to
the user to fetch URLs like to
http://somedomain.com/whatever?userID=1358f2d55b34fb581fd547
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/pr
22 matches
Mail list logo
