Re: [hybi] The future of WebSockets, and the WiSH proposal

Tobias Oberstein <tobias.oberstein@tavendo.de> Sat, 10 June 2017 13:18 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 A971A12896F for <hybi@ietfa.amsl.com>; Sat, 10 Jun 2017 06:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dhRNmU8yCxpK for <hybi@ietfa.amsl.com>; Sat, 10 Jun 2017 06:18:25 -0700 (PDT)
Received: from EXHUB020-5.exch020.serverdata.net (exhub020-5.exch020.serverdata.net [206.225.164.32]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9CBB4126CF9 for <hybi@ietf.org>; Sat, 10 Jun 2017 06:18:25 -0700 (PDT)
Received: from [192.168.1.73] (91.55.252.52) by smtpx20.serverdata.net (206.225.164.37) with Microsoft SMTP Server (TLS) id 8.3.485.1; Sat, 10 Jun 2017 06:18:24 -0700
To: Andy Green <andy@warmcat.com>, Takeshi Yoshino <tyoshino@google.com>, Anne van Kesteren <annevk@annevk.nl>
CC: "hybi@ietf.org" <hybi@ietf.org>, Tobias Oberstein <tobias.oberstein@crossbario.com>
References: <CAH9hSJYpnp0FXt9SsrujJM4OHcXe=pryUtHmM6dmcpgG67hdBw@mail.gmail.com> <CADnb78iPu7ACqZkYJ6SqceE2JNtV+y6M3ojT5PdGmDVoqZHsyQ@mail.gmail.com> <CAH9hSJZk-t-UwOD0jnaKr_M4uoHYwsCKU256ZsKxoVgwuWzxnQ@mail.gmail.com> <20c1e950-2c04-70eb-2372-bc9ba11c2de1@warmcat.com>
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
Message-ID: <ec35df33-19f8-525a-c8c0-ea0b8d8600f1@tavendo.de>
Date: Sat, 10 Jun 2017 15:18:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20c1e950-2c04-70eb-2372-bc9ba11c2de1@warmcat.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Language: de-LU
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/hybi/crKy0oJcQO7J8qzd-oz8_48ol3U>
Subject: Re: [hybi] The future of WebSockets, and the WiSH proposal
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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 Jun 2017 13:18:28 -0000

>> The bottom of the background section of the I-D
>> (https://tools.ietf.org/html/draft-yoshino-wish-02#section-2) is
>> unintentionally (I forgot to update it) left to be talking about using
>> WiSH framing over fetch()/Streams to improve the WebSocket ecosystem
>> without introducing any dedicated browser code. This is also a
>> possible option though it requires developers to include Polyfill in
>> their code.
> 
> The basic problem underneath all this is the guys who defined http/2
> considered ws so declasse

This was also my impression, Google powerplay (in this case), trying to 
shove sth down everyones throat, mostly skewed towards their very 
specific interests.

HTTP/1.1 + caching + WebSocket is a complete solution that works for me, 
I just don't need HTTP/2 nor WebSocket over HTTP/2.

 From my point of view, the "future of WebSocket" is bright as the 
technology stands.

I'd rather take up another initiative at WebSocket multiplexing and/or 
message priorization extensions.

/Tobias