Re: HTTP/2 Upgrade with content?

Martin Thomson <martin.thomson@gmail.com> Fri, 13 March 2015 23:21 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ietf.org@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 E05D91A876B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 13 Mar 2015 16:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 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, 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 YPTi3Zxu3JsF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 13 Mar 2015 16:21:21 -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 C2FF01A8776 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 13 Mar 2015 16:21:18 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YWYpv-000430-1B for ietf-http-wg-dist@listhub.w3.org; Fri, 13 Mar 2015 23:17:47 +0000
Resent-Date: Fri, 13 Mar 2015 23:17:47 +0000
Resent-Message-Id: <E1YWYpv-000430-1B@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1YWYpm-00041I-V0 for ietf-http-wg@listhub.w3.org; Fri, 13 Mar 2015 23:17:38 +0000
Received: from mail-ob0-f169.google.com ([209.85.214.169]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <martin.thomson@gmail.com>) id 1YWYpm-0001up-Nd for ietf-http-wg@w3.org; Fri, 13 Mar 2015 23:17:38 +0000
Received: by obdfc2 with SMTP id fc2so994439obd.3 for <ietf-http-wg@w3.org>; Fri, 13 Mar 2015 16:17: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; bh=eSZ5C0pV+6qjhMNsYjfaGOJlSQCNz7j4HXJrSA7okis=; b=qVDaPKShNAmYSRWQ5EIyD7RGL6U1IDnn02dztep0XVX1Bob5fw+bBsjtiUE51QK9EU BukIiCGwSiEyE7X0tzgGuz2Kgw47c7TVl6zJWJra3awqLk/A4OHqr87H2AP4ovzX36gF 0nbJOHth7HfWn+VQPkl/L/O/zJ3brYwbFQt5tCaD4V4cONoaO2ebBwNvpdtD93l6yaIB IHvZwGzcrDoizLAl+iZxS9jtWDnxHNT9KRfgmDw76vOLIXNgGh1OcUccGqdH+S1Fm6cs DDEf37lMCkh5X5AqaZdoGzzNoSRR6xrddeZfgfOdQXWlPh86E12xVKUAVmPUrUmpqWvl uJtw==
MIME-Version: 1.0
X-Received: by 10.182.39.227 with SMTP id s3mr31635678obk.44.1426288632931; Fri, 13 Mar 2015 16:17:12 -0700 (PDT)
Received: by 10.202.86.20 with HTTP; Fri, 13 Mar 2015 16:17:12 -0700 (PDT)
In-Reply-To: <CAH_y2NGOzsgs3SuVcxNdMc76BcdNLUBKuK93aS9j-iJBfevDwA@mail.gmail.com>
References: <CAH_y2NF3iwND1ttQDY98KC_u=OZj5aqEABmXHKObMgqPH1npLg@mail.gmail.com> <BL2PR03MB1323474B977B051738AD09187060@BL2PR03MB132.namprd03.prod.outlook.com> <CAH_y2NFV=Z7hqbtWTdiePRwUnhhRjiP8R_Ua7kmpZEkwXtxgEA@mail.gmail.com> <B5C01B7A-9215-4268-B189-E6281F425BF7@greenbytes.de> <alpine.DEB.2.11.1503130833190.13706@tvnag.unkk.fr> <6E036F2D-AED0-4323-ACCB-D8036168E6C1@redhat.com> <CAH_y2NFjb0mx8Rs+qg6uJ=zgUzHW3ksiOSN4_GXubKG-P2QDaw@mail.gmail.com> <CABkgnnWEx4+o34h70168ZYihs9MFZQ=SNQekNX1gdjq51=-k7g@mail.gmail.com> <CAH_y2NGOzsgs3SuVcxNdMc76BcdNLUBKuK93aS9j-iJBfevDwA@mail.gmail.com>
Date: Fri, 13 Mar 2015 16:17:12 -0700
Message-ID: <CABkgnnV1-n6JLnqKn5XcwmbyUR7At5vHfwVszsiMsQGXnT5oMg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Greg Wilkins <gregw@intalio.com>
Cc: "Jason T. Greene" <jason.greene@redhat.com>, Daniel Stenberg <daniel@haxx.se>, Stefan Eissing <stefan.eissing@greenbytes.de>, Mike Bishop <Michael.Bishop@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.214.169; envelope-from=martin.thomson@gmail.com; helo=mail-ob0-f169.google.com
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP/2 Upgrade with content?
Archived-At: <http://www.w3.org/mid/CABkgnnV1-n6JLnqKn5XcwmbyUR7At5vHfwVszsiMsQGXnT5oMg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/28971
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 13 March 2015 at 15:15, Greg Wilkins <gregw@intalio.com> wrote:
> Consider an app that performs some kind of streaming translation of the
> posted content into the response.  It will be reading chunks of the HTTP/1.1
> response and sending that as frames of HTTP/2 response.  Eventually the
> stream/connection "window" will be consumed, but a window update frame will
> not be able to be sent because the HTTP/1.1 response is not complete.

Fair point; I hadn't thought the flow control aspects through fully.