Re: http/2 flow control
Roberto Peon <grmocg@gmail.com> Thu, 24 January 2013 22:37 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 1DF3E11E80D1 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 24 Jan 2013 14:37:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.398
X-Spam-Level:
X-Spam-Status: No, score=-10.398 tagged_above=-999 required=5 tests=[AWL=0.200, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FeNXosCyekLv for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 24 Jan 2013 14:37:47 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id CFD1811E8099 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 24 Jan 2013 14:37:42 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1TyVQ2-0006ia-MS for ietf-http-wg-dist@listhub.w3.org; Thu, 24 Jan 2013 22:37:14 +0000
Resent-Date: Thu, 24 Jan 2013 22:37:14 +0000
Resent-Message-Id: <E1TyVQ2-0006ia-MS@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1TyVPw-0006fy-Jh for ietf-http-wg@listhub.w3.org; Thu, 24 Jan 2013 22:37:08 +0000
Received: from mail-lb0-f169.google.com ([209.85.217.169]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1TyVPu-0002Dz-V5 for ietf-http-wg@w3.org; Thu, 24 Jan 2013 22:37:08 +0000
Received: by mail-lb0-f169.google.com with SMTP id m4so6902449lbo.28 for <ietf-http-wg@w3.org>; Thu, 24 Jan 2013 14:36:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=CV+w/ZBO5Q6gsTqK+2TdmXhEzyOdKgFoKGoU3Z76M6M=; b=Z8EmgMaDUH+SHN2crYBYWfq7rfxP/CGqO27DIidcRWe4gSVPwZWKqxJHcQfvYsZVse sK+iV++6LCvUQiz3oBAaVI3ZvmztA5FPRDm4rwdS0c9rBW7oFK1UhM+MV/Z8amBNBetG mOAD5KJc4jqXa6QF/+U56lCUf6kKF2J/OBJ/0DSesx9JUfEKoN4tebOxvRQDO+5r9RtS daLw1LGecJq7ykKLdnYeoM/XbN/xG4rhkmvy1V2M7dMhze9vL3VX38D0wlZt2P4shiB4 zBvpJZELoiHZmgO5tatRGRNJkBDOWySS/GISUzp36C5VAm86eUv1/jNj3YZKRWtkeSuZ CE6g==
MIME-Version: 1.0
X-Received: by 10.112.51.44 with SMTP id h12mr1362497lbo.111.1359067000198; Thu, 24 Jan 2013 14:36:40 -0800 (PST)
Received: by 10.112.81.5 with HTTP; Thu, 24 Jan 2013 14:36:40 -0800 (PST)
In-Reply-To: <CAK3OfOiR11N0bW1Ac6=iLqsGzfFH+YLyjAmJCoPmJuruUQ3Dyg@mail.gmail.com>
References: <CAA4WUYgk-NPZ0bdYV3KysVED=OqFQ6Z0eE-7ePmmFdS2GMfjLA@mail.gmail.com> <CAK3OfOiR11N0bW1Ac6=iLqsGzfFH+YLyjAmJCoPmJuruUQ3Dyg@mail.gmail.com>
Date: Thu, 24 Jan 2013 14:36:40 -0800
Message-ID: <CAP+FsNcFn2HSMRpCZ=c4xvPSpdjJUoAsptcritc6K0KjD4uYuA@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: "William Chan (陈智昌)" <willchan@chromium.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="f46d04017147c5d87a04d41071b1"
Received-SPF: pass client-ip=209.85.217.169; envelope-from=grmocg@gmail.com; helo=mail-lb0-f169.google.com
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-2.586, 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
X-W3C-Scan-Sig: maggie.w3.org 1TyVPu-0002Dz-V5 6dfe1ed288b37035cc55635f3910ce3d
X-Original-To: ietf-http-wg@w3.org
Subject: Re: http/2 flow control
Archived-At: <http://www.w3.org/mid/CAP+FsNcFn2HSMRpCZ=c4xvPSpdjJUoAsptcritc6K0KjD4uYuA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16190
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>
Will's naming in his email wasn't the best :) Flow control in SPDY3 was flawed and didn't work. It was solely per-stream flow control. What is proposed in his writeup fixes this flaw relatively simply. The most relevant line is: It’s important to recognize that stream and session flow control serve two separate roles. Session flow control helps manage the memory consumption per session, whereas stream flow control helps manage what portion of that that memory an individual stream is allowed consume. I suggest reading the doc, though! -=R On Thu, Jan 24, 2013 at 2:31 PM, Nico Williams <nico@cryptonector.com>wrote: > Quick question: is the flow control in SPDY 3 like SSHv2's? I.e., > with per-flow window sizes advertised by the receiver? > > I ask because this has caused serious problems in the SSH world. I > don't want HTTP/2.0 to make the same mistakes. > > Nico > -- > >
- http/2 flow control William Chan (陈智昌)
- Re: http/2 flow control Nico Williams
- Re: http/2 flow control Roberto Peon
- Re: http/2 flow control Nico Williams
- Re: http/2 flow control Mike Belshe