Re: Push and Caching
Martin Thomson <martin.thomson@gmail.com> Tue, 26 August 2014 23:24 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1781A00FF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 26 Aug 2014 16:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.67
X-Spam-Level:
X-Spam-Status: No, score=-7.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.668, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X-6eU-rYiP9N for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 26 Aug 2014 16:24:44 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ECE871A0033 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 26 Aug 2014 16:24:43 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XMQ4q-0002vK-3l for ietf-http-wg-dist@listhub.w3.org; Tue, 26 Aug 2014 23:23:00 +0000
Resent-Date: Tue, 26 Aug 2014 23:23:00 +0000
Resent-Message-Id: <E1XMQ4q-0002vK-3l@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1XMQ4W-0002oU-Tn for ietf-http-wg@listhub.w3.org; Tue, 26 Aug 2014 23:22:40 +0000
Received: from mail-lb0-f180.google.com ([209.85.217.180]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1XMQ4W-0001jw-5i for ietf-http-wg@w3.org; Tue, 26 Aug 2014 23:22:40 +0000
Received: by mail-lb0-f180.google.com with SMTP id 10so2190379lbg.39 for <ietf-http-wg@w3.org>; Tue, 26 Aug 2014 16:22:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=9HCik7IIRc6XnlmWVBlB2mzH+Xm/VAb4o64NXxhW2lk=; b=hG2hO3aM21g9UjEWbQ+Id6wvYNfVMCeZCKQCSAdT/jyCk4ZMPRhotZG6+CVrisIJc4 WSZ9U5mvmj8mISSbIbys3GxqKvpzKGzUy0zjd7XL1lOz8FnB/Bzpgn1p+3xXx1FHEKM4 D77wvXWiIKz9ge3oKhU6LaKLPai0qNa5W+vFHh223X9m/eAgAChTupY0Jd84X5HwPlZh pR4z7rNrL/1f9TaHoH2eJ953SJ1buxeCmUtlHe8YhMc1VE06973t4bN6rviYKAYkMfc8 FPadJuEDyx4I+LxhFwoqiuEn6ZMRcgmbHqRIgg8Js7AK/PxmjTkLak5i3/Y5NZ/43Ggh mAWQ==
MIME-Version: 1.0
X-Received: by 10.152.88.81 with SMTP id be17mr17258974lab.75.1409095333419; Tue, 26 Aug 2014 16:22:13 -0700 (PDT)
Received: by 10.25.166.75 with HTTP; Tue, 26 Aug 2014 16:22:13 -0700 (PDT)
In-Reply-To: <ee6c28ad51ab4022a6346ffb836bf770@DM2PR05MB670.namprd05.prod.outlook.com>
References: <dc3d860ecb4b4d408a5ed0519a036e61@BL2PR03MB132.namprd03.prod.outlook.com> <CABkgnnWvKgyDcm-1jEKZUA2Qza9M46X+X_QybwuqRwvSUrTjNw@mail.gmail.com> <B6B89855-237F-44DA-B29C-2A3BB5CE0EED@mnot.net> <920b92b90a3c47ef8d450c903b83af40@DM2PR05MB670.namprd05.prod.outlook.com> <d94a3acceb954583a61b0118381df417@BL2PR03MB132.namprd03.prod.outlook.com> <CAOdDvNpa5WR4LJbsgQaBE3bTSAc+gXfYqCmV+zmUzE5b7+1a9A@mail.gmail.com> <CECA0C1A-E64C-443A-87AF-22BC66286F72@mnot.net> <CABkgnnXVJA3R4qhc__k4j+_LzeS7B24VxfCZwBSfywepEx=tKA@mail.gmail.com> <40d03e3bb1df480e808e64fa29048880@BL2PR03MB132.namprd03.prod.outlook.com> <CABkgnnX-0X+JZfFYhm18b=bLidaq_pqN5s-K0NBS28m-s6+9Kg@mail.gmail.com> <233C8C21-BF80-4E07-9717-56630085E192@mnot.net> <CABkgnnW9Uq5R1KvuTXuT=xUdX_pVWikyAOMp=ixJe+c0NRs4Lg@mail.gmail.com> <CAH_y2NHV_966DSX4yX-=tfDPUkk-obCXFbJnPifQpFb1KFjYDg@mail.gmail.com> <7d2fdc975fec4646b21e86620a834e72@DM2PR05MB670.namprd05.prod.outlook.com> <2C38B85E-7290-4AE3-A886-12A329DE449C@mnot.net> <D92F296B-3E9A-42B3-978C-AC319C072C60@mnot.net> <9C64D35C-49BF-47F7-8D72-EFA2DA546FEA@gbiv.com> <22238EC5-50F4-4611-9FED-39E3D7B67B10@gbiv.com> <CABkgnnWssBqVw+aSb_8y80JBRWkQ8H+MPvmYZ7MyzOkYUQwWTQ@mail.gmail.com> <DE38D1FB-C9E1-441F-BDCE-9258714E0D96@gbiv.com> <02fc4b73d8004853b4286d02acbcc942@DM2PR05MB670.namprd05.prod.outlook.com> <CABkgnnWXiivor8cTrHiAsL8uyJ-42FsiF44_103c7M+w2e797A@mail.gmail.com> <ee6c28ad51ab4022a6346ffb836bf770@DM2PR05MB670.namprd05.prod.outlook.com>
Date: Tue, 26 Aug 2014 16:22:13 -0700
Message-ID: <CABkgnnUXs=0U_m6bX4g=B9w+MnXdixe_Vo=HnCcAp8NgtE7xpA@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: William Chow <wchow@mobolize.com>
Cc: "Roy T. Fielding" <fielding@gbiv.com>, Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.217.180; envelope-from=martin.thomson@gmail.com; helo=mail-lb0-f180.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.723, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1XMQ4W-0001jw-5i ff1fa56358f2402323bc6f96355265e3
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Push and Caching
Archived-At: <http://www.w3.org/mid/CABkgnnUXs=0U_m6bX4g=B9w+MnXdixe_Vo=HnCcAp8NgtE7xpA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26754
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 26 August 2014 16:07, William Chow <wchow@mobolize.com> wrote: > What I am hoping we'd be able to do is to include language that describes the relationship between the original request/response and the pushed responses, so that caches have guidance on when it is safe to serve a pushed response when the client-initiated request is actually received later from the UA. Any association between a request and any server pushes it generates is largely incidental from the perspective of what we are talking about right now (caching, validity, general usability). Each request-response pair can be considered completely independent in that regard, in fact, in virtually all respects. Caches can and should treat each independently. The only tricky part is to determine when it is best to push something when you don't have any cues from the server. You could, for instance, remember the set of pushed resources that came in response to a given request and push those too, or you could build new heuristics around push for origin servers that don't generate it. That's something that is up to you.
- Push and Caching Mike Bishop
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Greg Wilkins
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Mark Nottingham
- RE: Push and Caching William Chow
- RE: Push and Caching Mike Bishop
- Re: Push and Caching Patrick McManus
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Martin Thomson
- RE: Push and Caching Mike Bishop
- Re: Push and Caching Martin Thomson
- RE: Push and Caching Mike Bishop
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Greg Wilkins
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Greg Wilkins
- RE: Push and Caching William Chow
- Re: Push and Caching Mark Nottingham
- RE: Push and Caching William Chow
- Re: Push and Caching Matthew Kerwin
- Re: Push and Caching Mark Nottingham
- Re: Push and Caching Chris Drechsler
- Re: Push and Caching Roy T. Fielding
- Re: Push and Caching Roy T. Fielding
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Roy T. Fielding
- Re: Push and Caching Michael Sweet
- RE: Push and Caching William Chow
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Roy T. Fielding
- RE: Push and Caching William Chow
- Re: Push and Caching Greg Wilkins
- Re: Push and Caching Greg Wilkins
- Re: Push and Caching Martin Thomson
- Re: Push and Caching Greg Wilkins