IETF Logo Mail Archive

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

Mark Nottingham <mnot@mnot.net> Tue, 22 January 2013 04:07 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC1711E80A5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 21 Jan 2013 20:07:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.574
X-Spam-Level:
X-Spam-Status: No, score=-9.574 tagged_above=-999 required=5 tests=[AWL=1.025, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rtjgBg-EIJr for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 21 Jan 2013 20:07:46 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id EE71C11E80B8 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 21 Jan 2013 20:07:45 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1TxV8M-0003kE-Ho for ietf-http-wg-dist@listhub.w3.org; Tue, 22 Jan 2013 04:06:50 +0000
Resent-Date: Tue, 22 Jan 2013 04:06:50 +0000
Resent-Message-Id: <E1TxV8M-0003kE-Ho@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1TxV8H-0003jU-RO for ietf-http-wg@listhub.w3.org; Tue, 22 Jan 2013 04:06:45 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by maggie.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1TxV8H-0002iL-5W for ietf-http-wg@w3.org; Tue, 22 Jan 2013 04:06:45 +0000
Received: from [192.168.1.80] (unknown [118.209.240.13]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1824722E1F4; Mon, 21 Jan 2013 23:06:22 -0500 (EST)
Content-Type: text/plain; charset="iso-8859-1"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAP+FsNeCZG1b35JEpyNgVo+3BpAEFSiOCOnHb=iNPfkQcuB92Q@mail.gmail.com>
Date: Tue, 22 Jan 2013 15:06:18 +1100
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B5885129-0A58-421E-BEEC-BC1F9E829FD0@mnot.net>
References: <20130121233617.11829.39388.idtracker@ietfa.amsl.com> <811EDF18-4B55-4732-8307-F6B4E0F07DF6@free.fr> <CAP+FsNesBJ_s15StYJLJoSOSJyB+Yx3C8p7kMiK_qH_9Q1F-Nw@mail.gmail.com> <FF21A5E5-0F41-45BE-8A08-7915E9632A86@mnot.net> <CAP+FsNeCZG1b35JEpyNgVo+3BpAEFSiOCOnHb=iNPfkQcuB92Q@mail.gmail.com>
To: Roberto Peon <grmocg@gmail.com>
X-Mailer: Apple Mail (2.1499)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: AWL=-2.317, BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1TxV8H-0002iL-5W bcce085497e062baddc0b68dd109d3ef
X-Original-To: ietf-http-wg@w3.org
Subject: Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt)
Archived-At: <http://www.w3.org/mid/B5885129-0A58-421E-BEEC-BC1F9E829FD0@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16092
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On 22/01/2013, at 3:01 PM, Roberto Peon <grmocg@gmail.com> wrote:

> The same way one would in a non-push world-- determine if it is mobile and serve the most appropriate content... :)

Yes and no. Today, you have the option of doing it server-side *or* client-side. When the server is pushing, all the decisions are made server-side. That means, for example, that it'll be potentially more difficult to server a responsive site that's completely static.


--
Mark Nottingham   http://www.mnot.net/

v2.23.0 | Report a Bug | By Email