IETF Logo Mail Archive

Re: [#153] PUSH_PROMISE headers

Yoav Nir <ynir@checkpoint.com> Sat, 29 June 2013 09:16 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 8234521F9808 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 29 Jun 2013 02:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7gy0t4qJjgl for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 29 Jun 2013 02:16:42 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 0767F21F96EB for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 29 Jun 2013 02:16:41 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UsrFc-0003Mm-9C for ietf-http-wg-dist@listhub.w3.org; Sat, 29 Jun 2013 09:15:24 +0000
Resent-Date: Sat, 29 Jun 2013 09:15:24 +0000
Resent-Message-Id: <E1UsrFc-0003Mm-9C@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <ynir@checkpoint.com>) id 1UsrFN-0003Lv-Cl for ietf-http-wg@listhub.w3.org; Sat, 29 Jun 2013 09:15:09 +0000
Received: from smtp.checkpoint.com ([194.29.34.68]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <ynir@checkpoint.com>) id 1UsrFM-0007Cc-8m for ietf-http-wg@w3.org; Sat, 29 Jun 2013 09:15:09 +0000
Received: from IL-EX10.ad.checkpoint.com ([194.29.34.147]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id r5T9EeZr013679 for <ietf-http-wg@w3.org>; Sat, 29 Jun 2013 12:14:40 +0300
X-CheckPoint: {51CEA580-B-1B221DC2-1FFFF}
Received: from DAG-EX10.ad.checkpoint.com ([169.254.3.48]) by IL-EX10.ad.checkpoint.com ([169.254.2.180]) with mapi id 14.02.0342.003; Sat, 29 Jun 2013 12:14:40 +0300
From: Yoav Nir <ynir@checkpoint.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Thread-Topic: [#153] PUSH_PROMISE headers
Thread-Index: AQHOdF66jzFw0PG1DUC2yyg7Jvl3xplL65eAgAADH4CAABNVgIAANQiA
Date: Sat, 29 Jun 2013 09:14:39 +0000
Message-ID: <BB0F14DE-65AB-417E-919C-04A5D2E2EB8E@checkpoint.com>
References: <CABkgnnVGh9dLkfDrO2fq5TsnxwEu0Dff=LqJEJR5Odq2ibfDMg@mail.gmail.com> <CABP7RbcoSSSKJq3YbZ2ypw-xb0uOgFQcjcQP9tJdkgEjPfJVMA@mail.gmail.com> <CAP+FsNdJcZ_x6RidaVfP+VPtA3CwAbALgAqhOhAjZLzaz4tQRQ@mail.gmail.com> <alpine.LRH.2.01.1306282202060.24949@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1306282202060.24949@egate.xpasc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.20.118]
x-kse-antivirus-interceptor-info: protection disabled
x-cpdlp: 11ac3df8c4bb6d2b9bd06f105cb2f3a6960a917a11
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A74D904B4AD38A468887E49457E8D629@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Received-SPF: pass client-ip=194.29.34.68; envelope-from=ynir@checkpoint.com; helo=smtp.checkpoint.com
X-W3C-Hub-Spam-Status: No, score=-6.5
X-W3C-Hub-Spam-Report: AWL=-0.214, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.303, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1UsrFM-0007Cc-8m 4c051a7118b49d0bcbef78bf1983635e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: [#153] PUSH_PROMISE headers
Archived-At: <http://www.w3.org/mid/BB0F14DE-65AB-417E-919C-04A5D2E2EB8E@checkpoint.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18416
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 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.

Another possible approach is statistical. Begin with the server not pushing any resources, and then collect statistics. What percentage of requests for index.html were followed by requests for logo.gif? If that percentage is high enough, you add logo.gif to the resources pushed following index.html.  Once a resource is pushed, you keep another statistic of what percentages of pushes were rejected (with RST_STREAM). If that's above a certain (low) threshold, you stop pushing it. 

Done this way, pushes will be mostly successful, and I don't see why they would waste significant bandwidth for the server.

Yoav

v2.23.0 | Report a Bug | By Email