Re: "Timeout" request header to tell server to wait for resource to become available
Martin Thomson <martin.thomson@gmail.com> Mon, 30 March 2015 15:25 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 F01331AC409 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Mar 2015 08:25:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 sjJDnPDjx9zl for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 30 Mar 2015 08:25:00 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8C3601AD0BE for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 30 Mar 2015 08:25:00 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YcbVA-0003Kj-5X for ietf-http-wg-dist@listhub.w3.org; Mon, 30 Mar 2015 15:21:20 +0000
Resent-Date: Mon, 30 Mar 2015 15:21:20 +0000
Resent-Message-Id: <E1YcbVA-0003Kj-5X@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1YcbUy-0003Ac-ME for ietf-http-wg@listhub.w3.org; Mon, 30 Mar 2015 15:21:08 +0000
Received: from mail-ob0-f170.google.com ([209.85.214.170]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1YcbUx-0004gb-La for ietf-http-wg@w3.org; Mon, 30 Mar 2015 15:21:08 +0000
Received: by obbgh1 with SMTP id gh1so61775704obb.1 for <ietf-http-wg@w3.org>; Mon, 30 Mar 2015 08:20:41 -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; bh=zlUdYbWprum2z3cqOel8meSjsrI9taENyDQUhB+1gSg=; b=Lmfu0utNWiS/URgAIC0GKAt3SMLjfYNirJnA04K392XIiRUHKeU54FhaNZsgJkyxSl k76Ywywros0rWZ3wdSfpO9cO3BCKodWHEbqFBaYPn9FbVIwsGCxAEMz3PePnrAYuPnjU qWADJeEqW8TeBtj/AkiR6tzr0JgNJMKsPQlwO0Fe5glZ53godw6ZzcuhuaHA/OBVEOUf MfAC/dxbb/q2ETk84OZwMffYUa3Eonz3+jlD9pSt8O3Z3cb/hYcNQD6KxDX5N0eLJQPX 2mIVJ0xOTHkirV6D+NhSoTlZcrV0jCqKmNSxRIbm0UBy/+5xj3jF8NQ4URxYZzP7QP/J kyfA==
MIME-Version: 1.0
X-Received: by 10.60.56.39 with SMTP id x7mr27298392oep.65.1427728840954; Mon, 30 Mar 2015 08:20:40 -0700 (PDT)
Received: by 10.202.48.151 with HTTP; Mon, 30 Mar 2015 08:20:40 -0700 (PDT)
Received: by 10.202.48.151 with HTTP; Mon, 30 Mar 2015 08:20:40 -0700 (PDT)
In-Reply-To: <55181B76.5060008@brendanlong.com>
References: <5515D627.1000106@brendanlong.com> <CABkgnnW1hR=utRNAYJhYDLtQiofAjdCYj1UQyC13duNMmOA5Ng@mail.gmail.com> <55181B76.5060008@brendanlong.com>
Date: Mon, 30 Mar 2015 08:20:40 -0700
Message-ID: <CABkgnnV2AKxCXEmmjPhGwYTfRwQprO+zxCoqudmPG61TWtz-yg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Brendan Long <self@brendanlong.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a11c252c866ac930512830600"
Received-SPF: pass client-ip=209.85.214.170; envelope-from=martin.thomson@gmail.com; helo=mail-ob0-f170.google.com
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: AWL=1.846, BAYES_00=-1.9, 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, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: maggie.w3.org 1YcbUx-0004gb-La 0b3c014b5f88df31683d2a243eb37aee
X-Original-To: ietf-http-wg@w3.org
Subject: Re: "Timeout" request header to tell server to wait for resource to become available
Archived-At: <http://www.w3.org/mid/CABkgnnV2AKxCXEmmjPhGwYTfRwQprO+zxCoqudmPG61TWtz-yg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29075
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 Mar 29, 2015 8:34 AM, "Brendan Long" <self@brendanlong.com> wrote: > > I don't think the semantics I want are the same. RFC 7240's "wait" > indicates how long a client is willing to wait for a server to finish > processing, but what I'm looking for is a way to tell the server that we > want it to wait, even though it could respond now. > > Maybe the "Wait-Until: available" or "Wait-Until: etags-change" variant > makes this more clear? If-None-Match in combination with Prefer: wait does exactly what you want here.
- ***UNCHECKED*** "Timeout" request header to tell … Brendan Long
- Re: "Timeout" request header to tell server to wa… Martin Thomson
- Re: "Timeout" request header to tell server to wa… Matthew Kerwin
- Re: "Timeout" request header to tell server to wa… Brendan Long
- Re: "Timeout" request header to tell server to wa… Amos Jeffries
- Re: "Timeout" request header to tell server to wa… Martin Thomson
- Re: "Timeout" request header to tell server to wa… Brendan Long
- Re: "Timeout" request header to tell server to wa… Benjamin Carlyle
- Re: "Timeout" request header to tell server to wa… Martin Thomson