Re: [hybi] WebSocket subprotocol parameters

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Tue, 21 January 2014 09:17 UTC

Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6674B1A00A1 for <hybi@ietfa.amsl.com>; Tue, 21 Jan 2014 01:17:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.926
X-Spam-Level:
X-Spam-Status: No, score=-1.926 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
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 d1jeeLY8NJbC for <hybi@ietfa.amsl.com>; Tue, 21 Jan 2014 01:17:41 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0B65F1A00A2 for <hybi@ietf.org>; Tue, 21 Jan 2014 01:17:39 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id s0L9HSS2008242; Tue, 21 Jan 2014 18:17:29 +0900
Received: from (unknown [133.2.206.134]) by scmse02.scbb.aoyama.ac.jp with smtp id 6b24_316e_d9756f6c_827c_11e3_a1b5_001e6722eec2; Tue, 21 Jan 2014 18:17:28 +0900
Received: from [IPv6:::1] (unknown [133.2.210.1]) by itmail2.it.aoyama.ac.jp (Postfix) with ESMTP id E70F2BF4E2; Tue, 21 Jan 2014 18:17:27 +0900 (JST)
Message-ID: <52DE3B1B.1010804@it.aoyama.ac.jp>
Date: Tue, 21 Jan 2014 18:17:15 +0900
From: "\"Martin J. Dürst\"" <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Peter Thorson <webmaster@zaphoyd.com>
References: <634914A010D0B943A035D226786325D4446BF9948F@EXVMBX020-12.exch020.serverdata.net> <52D90F99.6080205@gmx.de> <634914A010D0B943A035D226786325D4446BF9949D@EXVMBX020-12.exch020.serverdata.net> <CAH9hSJZQ3NxVW36PnZ0TpMF4tPPaJLr12M8NtbPb6pUejf1wcQ@mail.gmail.com> <634914A010D0B943A035D226786325D4446BF99977@EXVMBX020-12.exch020.serverdata.net> <B8ED6F18-B710-44AE-829B-EDE5859B2C5B@zaphoyd.com>
In-Reply-To: <B8ED6F18-B710-44AE-829B-EDE5859B2C5B@zaphoyd.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: quoted-printable
Cc: Julian Reschke <julian.reschke@gmx.de>, "hybi@ietf.org" <hybi@ietf.org>
Subject: Re: [hybi] WebSocket subprotocol parameters
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.15
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, 21 Jan 2014 09:17:43 -0000

On 2014/01/21 0:58, Peter Thorson wrote:
> My impression was that subprotocol primarily changed the interpretation of messages payloads by the end applications themselves. WebSocket messages allow essentially arbitrary data so you can define whatever parameter setting mechanism you like with whatever grammar makes sense for your subprotocol and send the parameters in the opening “hello” message. Defining a grammar in the socket spec to allow application protocols to configure themselves seems limiting and out of scope.

Yes indeed. It has always been my impression that even subprotocols 
themselves are rather unnecessary. On the server side, just use a 
different URI/IRI as endpoint. On the client side, it's all JS anyway.

Regards,   Martin.