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

Simone Bordet <sbordet@intalio.com> Tue, 04 June 2013 10:27 UTC

Return-Path: <simone.bordet@gmail.com>
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 E62BB21F9B2B for <hybi@ietfa.amsl.com>; Tue, 4 Jun 2013 03:27:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 ovtB4R4aKWBn for <hybi@ietfa.amsl.com>; Tue, 4 Jun 2013 03:27:19 -0700 (PDT)
Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) by ietfa.amsl.com (Postfix) with ESMTP id 3216821F84B5 for <hybi@ietf.org>; Tue, 4 Jun 2013 02:21:29 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id v10so1932867pde.18 for <hybi@ietf.org>; Tue, 04 Jun 2013 02:21:15 -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 :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tyuNnyPx2DVhp/AcyZsLWhACuH6KFwZixw0ENU++TMc=; b=d9vRfMCC6PFHHkuHrVNjttuSTkJ0m7QnSAjR7Wzz09SVCK04fShBGVhaUY+2inwSDk Tl03Tng4us/ZiQbWFaW6CLWWbMCu5em+9VVjkYT21NqjkjlAErXP66KPOPEcVlSsjBJM 8/XYbqFPNsbq5B/jHKhc9U/IjBBhySToGvkn9N/CZIY7Aj/gDEzmvo5HCVf4qn100cDn TiX33Bkf75B1s64ICvPRUQ2fXlw0HW09+qvMbgxpPiaflo2iCGOWw8H46RTvoQhyTIhF NaeTyVhblSrAvwRnkCpH+DumngmyHReyK2whPM9dFqizDSmU4KNbdRJDnAin5gkQBhRq UUBA==
MIME-Version: 1.0
X-Received: by 10.68.219.70 with SMTP id pm6mr27458398pbc.154.1370337675452; Tue, 04 Jun 2013 02:21:15 -0700 (PDT)
Sender: simone.bordet@gmail.com
Received: by 10.68.209.131 with HTTP; Tue, 4 Jun 2013 02:21:15 -0700 (PDT)
In-Reply-To: <634914A010D0B943A035D226786325D4422DC2133A@EXVMBX020-12.exch020.serverdata.net>
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> <CAFWmRJ2Hbe0x5FeV2T7Gkp3WEsxQHe2=YPBTgvHYLcus3A4rBQ@mail.gmail.com> <CAH9hSJYOPvsFPDXLOa29ASd8xavLdvfRK_cVd=Uc=Vaydz1O=w@mail.gmail.com> <CAFWmRJ2M0Gtoz80+6v+=0Ldm9+xE2brqD2shVcBPuNz+QGiKHg@mail.gmail.com> <634914A010D0B943A035D226786325D4422DC20DAA@EXVMBX020-12.exch020.serverdata.net> <CAGzyod7o8AR2WxNrkZ-WWb5nc3zAJMvWhpfNVaW26sregESyjQ@mail.gmail.com> <634914A010D0B943A035D226786325D4422DC2133A@EXVMBX020-12.exch020.serverdata.net>
Date: Tue, 4 Jun 2013 11:21:15 +0200
X-Google-Sender-Auth: cbbnKBlrufhZ5Z0vP4l52B79n9k
Message-ID: <CAFWmRJ1EJVjFV1o2OcAtz4e=BTuSgdzsw-gyAi-TW8+iTb-QWw@mail.gmail.com>
From: Simone Bordet <sbordet@intalio.com>
To: Tobias Oberstein <tobias.oberstein@tavendo.de>
Content-Type: text/plain; charset=UTF-8
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: Tue, 04 Jun 2013 10:27:34 -0000

Hi,

On Mon, Jun 3, 2013 at 11:33 PM, Tobias Oberstein
<tobias.oberstein@tavendo.de> wrote:
>>imho, we're reinventing SPDY/HTTP/2, and I'd rather implement the complexity of muxing, security, prioritization, flow-control, liveness-checking, stream initiation, and compression, only once.

FWIW, I am with Roberto here.

> First, lets admit: we are both biased;)
>
> What about HTTP/2 over WS?
>
> http://tools.ietf.org/html/draft-montenegro-httpbis-speed-mobility-02
>
> I prefer native WS. I do single-page web apps with app manifests.
>
> The attractiveness of SPDY(TM) (be it native or over WS) in this situation is limited. Any static resources are retrieved only once anyway, and any communication after that can be done via WS.
>
> - native WS is widely implemented today
> - native WS has lower per-message overhead than "WS over SPDY(TM)"
> - WS (now) has _payload_ compression
> - liveness checking => WS pings/pongs
> - security => WS masking, WS origin

Sure. But I fail to see why you need MUX for your use case. One duplex
connection seems enough to me.

> So I'd say a WS-MUX with flow-control (draft there) plus priorization/scheduling (not there) is "the last missing piece". Lets finish it.

The problem I see is that the 2 features you mention here are quite
complicated to specify and implement correctly, i.e. we duplicate the
larger effort undertaken by HTTP/2.

--
Simone Bordet
----
http://cometd.org
http://webtide.com
http://intalio.com
Developer advice, training, services and support
from the Jetty & CometD experts.
Intalio, the modern way to build business applications.