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

Simone Bordet <> Sun, 19 May 2013 18:37 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ABE9321F87C5 for <>; Sun, 19 May 2013 11:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PDnXB1j3RNCA for <>; Sun, 19 May 2013 11:37:13 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400e:c01::22c]) by (Postfix) with ESMTP id C38E121F8733 for <>; Sun, 19 May 2013 11:37:13 -0700 (PDT)
Received: by with SMTP id wz12so459145pbc.3 for <>; Sun, 19 May 2013 11:37:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=usSgSCHsCOzVIdRRtQy+KNFE5dN4msDVSs31qrH+hsw=; b=poMyP6lPMtNvZOC/nUH724u9W3PQ07vOMhl5qBirHVapw1XkXPYha6YLFN9LgeL7SZ dHMXEl6mqI1xLePtrNv81fSu58MMcts3jIp3N0La1avI6X8eNWXbdJqQeXUo0qMoyKLg VGUqGlZHH3/SsmqI/OOdYG+vYNg2hnmw7AuU3d+eQfBYwX0tG7KOZ3lLF2hUtu4gSvff fG9R8TfOkdQGcHITMv2NvrwVZFFplKMkEuK88U6d9I1RO7BdXy72fsqxNo7CtKC6Vk2x 9RB9mSruKX/R5t46NK3ja+2xpjNCbWCGawean2/X8gAlX7HruB38V8XM3Sy3nbJSgf73 hdJQ==
MIME-Version: 1.0
X-Received: by with SMTP id uk5mr39703480pac.110.1368988633248; Sun, 19 May 2013 11:37:13 -0700 (PDT)
Received: by with HTTP; Sun, 19 May 2013 11:37:13 -0700 (PDT)
In-Reply-To: <>
References: <> <> <>
Date: Sun, 19 May 2013 20:37:13 +0200
X-Google-Sender-Auth: BahVMXytH0B0Xfuz92okx77Z_5k
Message-ID: <>
From: Simone Bordet <>
To: Takeshi Yoshino <>
Content-Type: text/plain; charset=UTF-8
Cc: "" <>
Subject: Re: [hybi] Call for interest: multiplexing dedicated for WebSocket
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 19 May 2013 18:37:14 -0000


On Sun, May 19, 2013 at 6:30 AM, Takeshi Yoshino <> wrote:
> I got one comment about this.
> He/she suggested that we finish the WebSocket dedicated multiplexing quickly
> even by simplifying the spec much e.g. cutting some functionality in it that
> would take much time to get consensus, and when HTTP/2.0 is matured, switch
> to that.

My impression is that I have not seen much request for WebSocket multiplexing.
Given the complexities related to defining and implementing ws mux
correctly, and considering that HTTP/2.0 comes with mux built-in,
building on the SPDY experience, my preference would be to
deprioritize ws mux in favour of HTTP/2.0 integration.
It is true that there may be systems that may rely on a pure-ws
communication (and therefore do not need a full HTTP/2.0
implementation) and as such would benefit from ws mux, but my guess is
that those system will be a minority or can get by without ws mux. I
may be biased on this view though, so comments welcome.

Thanks !

Simone Bordet
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.