W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2013

Re: [#153] PUSH_PROMISE headers

From: Michael Sweet <msweet@apple.com>
Date: Sun, 30 Jun 2013 21:52:05 -0400
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-id: <4097B961-AE6A-4D39-ACFD-EA06E35C9604@apple.com>
To: Yoav Nir <ynir@checkpoint.com>
I haven't had a proper amount of time to review the current draft, but I just wanted to throw something out...


On 2013-06-29, at 5:14 AM, Yoav Nir <ynir@checkpoint.com> wrote:
> 
> On Jun 29, 2013, at 9:04 AM, David Morris <dwm@xpasc.com> wrote:
> 
>> I continue to suspect that PUSH_PROMISE is either not going to be
>> heavily used on the general web or it is going to waste significant
>> bandwidth and server capacity. 
> 
> There's been very little talk (at list on-list) about how a server decides what resources to push. One way is to push down all the resources referenced from an HTML document. That would interact badly with caching, both in clients and in proxies.

Currently a client will send GET requests with If-Modified-Since for every resource it needs; perhaps if there was a way for the client to pass along a list of already-fetched resources with the fetch date, the server could push any new resources back to the client?

(that might defeat any performance advantage, or maybe not - something to try?)

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair
Received on Monday, 1 July 2013 01:52:47 UTC

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