Re: [hybi] Call for interest: multiplexing dedicated for WebSocket

Tobias Oberstein <tobias.oberstein@tavendo.de> Wed, 22 May 2013 17:40 UTC

Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2189D21F923B for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 10:40:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aWjGm1Sp0R7h for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 10:39:56 -0700 (PDT)
Received: from EXHUB020-2.exch020.serverdata.net (exhub020-2.exch020.serverdata.net [206.225.164.29]) by ietfa.amsl.com (Postfix) with ESMTP id 9822D21F915C for <hybi@ietf.org>; Wed, 22 May 2013 10:39:56 -0700 (PDT)
Received: from [10.157.82.16] (89.204.138.16) by smtpx20.serverdata.net (206.225.164.34) with Microsoft SMTP Server (TLS) id 8.3.264.0; Wed, 22 May 2013 10:39:53 -0700
Message-ID: <519D02E7.6040009@tavendo.de>
Date: Wed, 22 May 2013 19:39:51 +0200
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: "John A. Tamplin" <jat@jaet.org>
References: <CAH9hSJZxr+aG7GZa4f-dUOTGj4bnJ+3XxivUX4jei5CMyqN4LQ@mail.gmail.com> <CAH9hSJZUG1f+3Uk=t2=A5i4O9=wPvAisspM=pgmGEH9emTL9-Q@mail.gmail.com> <CAH9hSJZai_UuxW4O6mZcEJT2DJoURtLo16XNci1qkYVWv4HVdg@mail.gmail.com> <007501ce56f0$67f74080$37e5c180$@noemax.com> <519CD6A1.7080708@ericsson.com> <519CE075.4000106@tavendo.de> <CAM5k6X9WmO80hiQZ6_GqK66PAd3of=2ZRi9=VrWj52apA1+=5g@mail.gmail.com>
In-Reply-To: <CAM5k6X9WmO80hiQZ6_GqK66PAd3of=2ZRi9=VrWj52apA1+=5g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Call for interest: multiplexing dedicated for WebSocket
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 17:40:02 -0000

Am 22.05.2013 18:26, schrieb John A. Tamplin:
> On Wed, May 22, 2013 at 11:12 AM, Tobias Oberstein
> <tobias.oberstein@tavendo.de <mailto:tobias.oberstein@tavendo.de>> wrote:
>
>     +1 for the simplest possible mux that does the core job.
>
>     However, I currently think that having a per-logical channel flow
>     control is required to make it useful (cannot be dropped for the
>     sake of simplification). I might be wrong.
>
>
> I agree -- without flow control, there is very little benefit, and
> almost nothing that an app couldn't easily do themselves by just adding
> a simple framing layer inside WS messages (perhaps just the first byte
> is a logical channel number).

Regarding implementing flow control above TCP (and below app), I found this:

"Multiplexing on top of TCP in overall fails to deliver the advantages 
it is assumed to provide."

Source: http://www.250bpm.com/multiplexing

Do you have an opinion on that?

More important: what problem exactly does multiplexing solve? The 
current mux RFC mentions "scalability", but doesn't go into detail ..

/Tobias

>
> --
> John A. Tamplin