W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: Server Push -> Cache Push?

From: Mike Belshe <mike@belshe.com>
Date: Wed, 29 Jan 2014 16:46:44 -0800
Message-ID: <CABaLYCsbJw_d7FjaYn1wK5cFJM_8huP9sfXuTim04bs87EkKDg@mail.gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: httpbis mailing list <ietf-http-wg@w3.org>
I think server-push is actually pretty well understood.  Those versant in
HTTP recognize that a push to the server is also known as a "GET".

If we really think its a problem, maybe "server initiated streams"?

I think cache-push raises questions about which cache.  prefetch doesn't
seem to quite work because the client isn't fetching at all.

Overall, I like server push.


On Wed, Jan 29, 2014 at 4:33 PM, Amos Jeffries <squid3@treenet.co.nz> wrote:

> On 2014-01-30 13:07, Mark Nottingham wrote:
>> So, we've always talked about pushing into the cache; presumably, if
>> you push something that's no-cache, it has a special state that allows
>> it to be used once / within a browsing context, but it's still being
>> pushed into the cache (indeed, the HTTP caching model already talks
>> about caching things that are no-cache).
> How about some analog of "prefetch"?  it is essentially a server-initiated
> prefetch operation after all.
> Amos
Received on Thursday, 30 January 2014 00:47:12 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC