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

Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt)

From: Patrick McManus <pmcmanus@mozilla.com>
Date: Tue, 22 Jan 2013 09:53:57 -0500
Message-ID: <CAOdDvNrH0FLed_k2Q1Qzs9w_M4odpQpzexgz6JRUP5APgO6qMQ@mail.gmail.com>
To: Ilya Grigorik <ilya@igvita.com>
Cc: Mark Nottingham <mnot@mnot.net>, Roberto Peon <grmocg@gmail.com>, Frédéric Kayser <f.kayser@free.fr>, HTTP Working Group <ietf-http-wg@w3.org>
honestly I do think push can, and should, be refined a bit for reasons of
bandwidth (and cost) conservation in some envs. Even the notiion of
Have-Subresources:: etag set (or hash of set, or whatever) probly gets a
long way.


On Mon, Jan 21, 2013 at 11:20 PM, Ilya Grigorik <ilya@igvita.com> wrote:

>
> On Mon, Jan 21, 2013 at 7:35 PM, Mark Nottingham <mnot@mnot.net> wrote:
>
>> Also, it'd be REALLY nice to think about about what this means for
>> responsive design; e.g., if I'm a mobile, I don't need the desktop
>> stylesheet, and maybe not some of those images too. So, how does that work
>> in a push world?
>
>
> I think these are mostly orthogonal. While its a good exercise to think
> about this, I don't think this needs to be an explicit goal for HTTP 2.0.
> The HTML5 spec specifically says that the resources should be downloaded,
> even if the media-query breakpoint does not match (ex, print stylesheet,
> etc). In other words, we need to first resolve these questions in HTML5
> specs, before we worry about the transport.. otherwise cart before the
> horse...
>
> And, all of that aside, we do have a solution: serve the appropriate HTML
> to different clients. (just add a Vary: User-Agent.. oh wait - *ducks* :-))
>
> ig
>
Received on Tuesday, 22 January 2013 14:54:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 22 January 2013 14:54:32 GMT