Re: h2 proxy and connection flow control
Patrick McManus <mcmanus@ducksong.com> Thu, 21 August 2014 14:15 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 1D9A11A86E1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 21 Aug 2014 07:15:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.947
X-Spam-Level:
X-Spam-Status: No, score=-6.947 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, 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 ix_MAXcX2clz for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 21 Aug 2014 07:15:50 -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 536FB1A0344 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 21 Aug 2014 07:15:50 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1XKT7R-0008RW-Jr for ietf-http-wg-dist@listhub.w3.org; Thu, 21 Aug 2014 14:13:37 +0000
Resent-Date: Thu, 21 Aug 2014 14:13:37 +0000
Resent-Message-Id: <E1XKT7R-0008RW-Jr@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <patrick.ducksong@gmail.com>) id 1XKT76-0008OC-QT for ietf-http-wg@listhub.w3.org; Thu, 21 Aug 2014 14:13:16 +0000
Received: from mail-qg0-f44.google.com ([209.85.192.44]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <patrick.ducksong@gmail.com>) id 1XKT76-0004PL-22 for ietf-http-wg@w3.org; Thu, 21 Aug 2014 14:13:16 +0000
Received: by mail-qg0-f44.google.com with SMTP id e89so8978052qgf.3 for <ietf-http-wg@w3.org>; Thu, 21 Aug 2014 07:12:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=d3TuJPEjJDZJDFOS7efW6tJPili3rSU3wd/n6eGKtyw=; b=Yi/SeSzjQX38uTbfDM7CQHS1sGOEN4ElRtZ6VW08leFwRO0R5gwDbgxyQMvdd34pU5 rhzF8VB1dNJeE4Yhsu84Kx8l95X5aDxYDzBQEymZFq2iN0I8HMnSHr8nmf+diOT6D5GF NXA2aeCyjQSdC8Dl3xIzq1JH0bPgfdiwGtwfsIkmfmHa1lj6lHgt838kOk7KE/b4R0o6 d7s9j4QvIeEwi6QsDyNwUv2VzuPyumhDn2PblRblS+4DwT54zIpdjPp/0J/omhR5/4I6 0cYmdoLr3dpGGcqV1nRAZwLhjwiOA/L8tt1EjkbFJkDW7oUROrRvjv/veqUDla2hYh+c 1ysg==
MIME-Version: 1.0
X-Received: by 10.224.223.199 with SMTP id il7mr74646385qab.10.1408630370251; Thu, 21 Aug 2014 07:12:50 -0700 (PDT)
Sender: patrick.ducksong@gmail.com
Received: by 10.140.104.161 with HTTP; Thu, 21 Aug 2014 07:12:50 -0700 (PDT)
In-Reply-To: <CAPyZ6=J1b6VYaBJ==H7FsO9ofe9BTv53+DoDTCeRtW8TPmx=Bw@mail.gmail.com>
References: <CAPyZ6=+9sEFaaEBHSvhbzck6mLthatDVamMckYfnUXVMhVbiVg@mail.gmail.com> <CAOdDvNqX0H7hhxtx3ODniuYQU5wt9Qi91BDjOcENssi_m4PbQA@mail.gmail.com> <CAPyZ6=J1b6VYaBJ==H7FsO9ofe9BTv53+DoDTCeRtW8TPmx=Bw@mail.gmail.com>
Date: Thu, 21 Aug 2014 10:12:50 -0400
X-Google-Sender-Auth: M15_vBCV415le68hVzZQX5pLxWg
Message-ID: <CAOdDvNr3g5Ch80ypTThNvZDPftPG5Qive6WmHrvHgsw4NEXOTA@mail.gmail.com>
From: Patrick McManus <mcmanus@ducksong.com>
To: Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com>
Cc: HTTP <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a11c22d8ad6bc8105012450c5"
Received-SPF: pass client-ip=209.85.192.44; envelope-from=patrick.ducksong@gmail.com; helo=mail-qg0-f44.google.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-2.705, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1XKT76-0004PL-22 8b04df97729a4dea584758da2380c5a6
X-Original-To: ietf-http-wg@w3.org
Subject: Re: h2 proxy and connection flow control
Archived-At: <http://www.w3.org/mid/CAOdDvNr3g5Ch80ypTThNvZDPftPG5Qive6WmHrvHgsw4NEXOTA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/26690
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 Thu, Aug 21, 2014 at 10:09 AM, Tatsuhiro Tsujikawa <tatsuhiro.t@gmail.com > wrote: > > > > In this scenario, proxy has no room to expand. Therefore I wrote that > all streams on backend connections are stalled. > > This is my point. If the proxy really has no room to expand (its out of ram) - then we've got a resource problem not a protocol problem. If it does have more ram, then just use the protocol to open the window to match the resources available.
- h2 proxy and connection flow control Tatsuhiro Tsujikawa
- Re: h2 proxy and connection flow control Patrick McManus
- Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
- Re: h2 proxy and connection flow control Patrick McManus
- Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
- Re: h2 proxy and connection flow control Amos Jeffries
- Re: h2 proxy and connection flow control Martin Thomson
- Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
- Re: h2 proxy and connection flow control Ilari Liusvaara
- Re: h2 proxy and connection flow control Tatsuhiro Tsujikawa
- Re: h2 proxy and connection flow control Martin Thomson