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

Tobias Oberstein <tobias.oberstein@tavendo.de> Wed, 22 May 2013 15:32 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 1ACD221F9051 for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 08:32:05 -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 pGztLh-JMgm0 for <hybi@ietfa.amsl.com>; Wed, 22 May 2013 08:31:59 -0700 (PDT)
Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) by ietfa.amsl.com (Postfix) with ESMTP id E640E21F92E7 for <hybi@ietf.org>; Wed, 22 May 2013 08:31:58 -0700 (PDT)
Received: from [10.157.82.16] (89.204.138.16) by smtpx20.serverdata.net (206.225.164.35) with Microsoft SMTP Server (TLS) id 8.3.264.0; Wed, 22 May 2013 08:31:57 -0700
Message-ID: <519CE4EC.30902@tavendo.de>
Date: Wed, 22 May 2013 17:31:56 +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: Salvatore Loreto <salvatore.loreto@ericsson.com>
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> <519CE300.40107@ericsson.com>
In-Reply-To: <519CE300.40107@ericsson.com>
Content-Type: text/plain; charset="windows-1252"; 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 15:32:05 -0000

Am 22.05.2013 17:23, schrieb Salvatore Loreto:
> <as individual>
>
> my concerns are just about the importance of WebSocket mux once HTTP/2.0
> will be finalized
> also considering the fact that the HTTP/2.0 standardization is
> proceeding quite fast and it is supposed
> to be finalized in one year and something

I would prefer a pure WS protocol (including mux and compression) _not_ 
layered on top of HTTP/2.0 as a long-term, widely implemented solution.

This is driven by our primary use case: have single-page web apps (with 
cached assets) that talk to backends exclusively over WS.

Layering WS on top of HTTP/2.0 does add additional overhead without 
gain, and for retrieving HTML etc assets that are persistently cached in 
browser (Web app manifests etc), HTTP/2.0 does not seem to add a lot 
over HTTP/1.1 also.

So personally I'd be fine with just WS and HTTP/1.1.

/Tobias