Re: How to stop receiving a pushed resource? (I-D Action: draft-ietf-httpbis-http2-01.txt)
Roberto Peon <grmocg@gmail.com> Tue, 22 January 2013 04:03 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 303AA11E80A5 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 21 Jan 2013 20:03:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.873
X-Spam-Level:
X-Spam-Status: No, score=-9.873 tagged_above=-999 required=5 tests=[AWL=0.725, BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 gZyeBYD70AzZ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 21 Jan 2013 20:03:16 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 1584611E8097 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 21 Jan 2013 20:03:16 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1TxV3w-00022y-LW for ietf-http-wg-dist@listhub.w3.org; Tue, 22 Jan 2013 04:02:16 +0000
Resent-Date: Tue, 22 Jan 2013 04:02:16 +0000
Resent-Message-Id: <E1TxV3w-00022y-LW@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1TxV3o-00022E-OJ for ietf-http-wg@listhub.w3.org; Tue, 22 Jan 2013 04:02:08 +0000
Received: from mail-lb0-f175.google.com ([209.85.217.175]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1TxV3n-0008UI-Mp for ietf-http-wg@w3.org; Tue, 22 Jan 2013 04:02:08 +0000
Received: by mail-lb0-f175.google.com with SMTP id n3so4563597lbo.20 for <ietf-http-wg@w3.org>; Mon, 21 Jan 2013 20:01:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=17EYfJjoNdTOVVm23EDIDyEBB6SkjCC4RQPWiz1w/YM=; b=xZfxNr07sr4z2qFvlB4NoyOVvgEeBpk9Wrtyh0wg2PPpgBCXIOvCumuEemwV2mdp9X O3pdfqAfBSqCuodc5RyGJFouPBn9XkBQ7xdOa++7vMjWerv3z/umEjElIEVQJvLl+VKE sK5focq8/DJ4jqRtZ/RWAMX1nslE4YKcBs5Z7SGT2exvFqsPV+j40ThtEWh7Q6iXtE2P l9Va+m5WTxni00BtVvHI56OC1Uik3flLIOU8HCa1D+8TuQHZZU9zd/B3l9O0p5Jtb8OS b0ZGfk3t7aIt0HbNK08PCfq7oi8GPU7gZ9QtotMlheTvH87uzotfIFalAF0biORyHT9l cmNA==
MIME-Version: 1.0
X-Received: by 10.112.11.33 with SMTP id n1mr8649978lbb.18.1358827301070; Mon, 21 Jan 2013 20:01:41 -0800 (PST)
Received: by 10.112.81.5 with HTTP; Mon, 21 Jan 2013 20:01:40 -0800 (PST)
In-Reply-To: <FF21A5E5-0F41-45BE-8A08-7915E9632A86@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>
Date: Mon, 21 Jan 2013 20:01:40 -0800
Message-ID: <CAP+FsNeCZG1b35JEpyNgVo+3BpAEFSiOCOnHb=iNPfkQcuB92Q@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Frédéric Kayser <f.kayser@free.fr>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="e0cb4efe2a309767be04d3d8a25a"
Received-SPF: pass client-ip=209.85.217.175; envelope-from=grmocg@gmail.com; helo=mail-lb0-f175.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.678, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1TxV3n-0008UI-Mp 391d876a1af87f3376dc2f6d51bf4879
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/CAP+FsNeCZG1b35JEpyNgVo+3BpAEFSiOCOnHb=iNPfkQcuB92Q@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16091
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 Mon, Jan 21, 2013 at 7:35 PM, Mark Nottingham <mnot@mnot.net> wrote: > I'd be interesting to hear what people running robots, etc. have to think > about this. > > 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? > The same way one would in a non-push world-- determine if it is mobile and serve the most appropriate content... :) -=R > > Personally -- the most immediate problem I have with this is figuring out > how to show push in REDbot :-/ > Cheers, > > > > On 22/01/2013, at 1:28 PM, Roberto Peon <grmocg@gmail.com> wrote: > > > Push is simply better inlining, with prioritization and cancellation. > > > > So, if you don't want a push, you'd cancel the stream, wasting at worst > one BDP worth of bandwidth, and at best near zero (since the push is > announced while the main resource is loading). > > > > Note that if server push is disabled, then servers will inline resources > which is strictly worse as it is impossible to prioritize or cancel (or > cache) such, leading to *increased * bandwidth usage and latency. > > > > -=R > > > > On Jan 21, 2013 5:38 PM, "Frédéric Kayser" <f.kayser@free.fr> wrote: > > Hello, > > is this the mechanism clients should use to stop receiving pushed > resources they already have in their local cache? > > How are servers supposed to guess what to push or not? Is it be based on > modification date, could the clients send some hints? > > > > Frédéric > > > > > 4.3.2. Client implementation > > > > > > When fetching a resource the client has 3 possibilities: > > > > > > the resource is not being pushed > > > > > > the resource is being pushed, but the data has not yet arrived > > > > > > the resource is being pushed, and the data has started to arrive > > > > > > When a SYN_STREAM and HEADERS frame which contains an Associated-To- > > > Stream-ID is received, the client must not issue GET requests for > the > > > resource in the pushed stream, and instead wait for the pushed > stream > > > to arrive. > > > > > > [...] > > > > > > To cancel individual server push streams, the client can issue a > > > stream error (Section 3.4.2) with error code CANCEL. Upon receipt, > > > the server MUST stop sending on this stream immediately (this is an > > > Abrupt termination). > > > > > > -- > Mark Nottingham http://www.mnot.net/ > > > >
- I-D Action: draft-ietf-httpbis-http2-01.txt internet-drafts
- How to stop receiving a pushed resource? (I-D Act… Frédéric Kayser
- Re: How to stop receiving a pushed resource? (I-D… William Chan (陈智昌)
- Re: How to stop receiving a pushed resource? (I-D… Roberto Peon
- Re: How to stop receiving a pushed resource? (I-D… Mark Nottingham
- Re: How to stop receiving a pushed resource? (I-D… Roberto Peon
- Re: How to stop receiving a pushed resource? (I-D… Mark Nottingham
- Re: How to stop receiving a pushed resource? (I-D… Ilya Grigorik
- Re: How to stop receiving a pushed resource? (I-D… Roberto Peon
- Re: How to stop receiving a pushed resource? (I-D… Frédéric Kayser
- Re: How to stop receiving a pushed resource? (I-D… Roberto Peon
- Re: How to stop receiving a pushed resource? (I-D… Patrick McManus
- Re: How to stop receiving a pushed resource? (I-D… Roberto Peon
- Re: How to stop receiving a pushed resource? (I-D… Karl Dubost