Re: [hybi] Multiplexing in WebSocket (Was: HyBi Design Space)

Julian Reschke <julian.reschke@gmx.de> Sat, 10 October 2009 09:51 UTC

Return-Path: <julian.reschke@gmx.de>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E313C28C102 for <hybi@core3.amsl.com>; Sat, 10 Oct 2009 02:51:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.83
X-Spam-Level:
X-Spam-Status: No, score=-3.83 tagged_above=-999 required=5 tests=[AWL=-3.090, BAYES_20=-0.74]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LnWSj1DYMdVO for <hybi@core3.amsl.com>; Sat, 10 Oct 2009 02:51:16 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id A754128C108 for <hybi@ietf.org>; Sat, 10 Oct 2009 02:51:15 -0700 (PDT)
Received: (qmail invoked by alias); 10 Oct 2009 09:53:00 -0000
Received: from p508FC6AB.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.198.171] by mail.gmx.net (mp070) with SMTP; 10 Oct 2009 11:53:00 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+WdyZ+i3yWP7W13yXT/Qx79k4yKsyJ7fyJjiAA1X guTvWARpjwRHFp
Message-ID: <4AD05971.7010001@gmx.de>
Date: Sat, 10 Oct 2009 11:52:49 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
References: <4ACE50A2.5070404@ericsson.com> <3a880e2c0910081600v3607665dp193f6df499706810@mail.gmail.com> <4ACF4055.6080302@ericsson.com> <Pine.LNX.4.62.0910092116010.21884@hixie.dreamhostps.com>
In-Reply-To: <Pine.LNX.4.62.0910092116010.21884@hixie.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.72
Cc: "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] Multiplexing in WebSocket (Was: HyBi Design Space)
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 10 Oct 2009 09:51:17 -0000

Ian Hickson wrote:
> ...
> FWIW, so far I've concluded (based on long discussions with a number of 
> developers and implementors) that multiplexing would actually not be that 
> great. It could probably only be used for multiplexing to a single 
> websocket path, without making the handshake highly asymmetric or breaking 
> the HTTP compatibility. If it's intended for per-client multiplexing, it 
> can easily be implemented at the application layer, where a much better 
> job can be done that could be done at the protocol layer. If it's intended 
> for multiclient multiplexing, then it's only helping server load, not 
> client performance, and server load isn't especially an issue here.
> ...

...why exactly is server load not an issue?

BR, Julian