IETF Logo Mail Archive

Re: [hybi] WebSocket subprotocol parameters

Tobias Oberstein <tobias.oberstein@tavendo.de> Mon, 20 January 2014 17:12 UTC

Return-Path: <tobias.oberstein@tavendo.de>
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 17C5C1A01D5 for <hybi@ietfa.amsl.com>; Mon, 20 Jan 2014 09:12:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 okqIGCLrnDBQ for <hybi@ietfa.amsl.com>; Mon, 20 Jan 2014 09:12:51 -0800 (PST)
Received: from EXHUB020-3.exch020.serverdata.net (exhub020-3.exch020.serverdata.net [206.225.164.30]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC101A0162 for <hybi@ietf.org>; Mon, 20 Jan 2014 09:12:51 -0800 (PST)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.11]) by EXHUB020-3.exch020.serverdata.net ([206.225.164.30]) with mapi; Mon, 20 Jan 2014 09:12:51 -0800
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Peter Thorson <webmaster@zaphoyd.com>
Date: Mon, 20 Jan 2014 09:12:48 -0800
Thread-Topic: [hybi] WebSocket subprotocol parameters
Thread-Index: Ac8V/D1Ae5jPSiwTRGOJCbF2SnIQEQABj9aQ
Message-ID: <634914A010D0B943A035D226786325D4446BF99B57@EXVMBX020-12.exch020.serverdata.net>
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> <634914A010D0B943A035D226786325D4446BF99ACB@EXVMBX020-12.exch020.serverdata.net> <82A1484B-1CDC-45BD-A2D2-6BED128F1448@zaphoyd.com>
In-Reply-To: <82A1484B-1CDC-45BD-A2D2-6BED128F1448@zaphoyd.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
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: Mon, 20 Jan 2014 17:12:53 -0000

>What do you gain by negotiating max_param1 at the subprotocol level vs negotiating "foo" as your subprotocol and having the foo protocol define how to negotiate its own settings via regular websocket messages?

If "param1" would influence how to parse raw WS payload into "foo" protocol, that would not be possible.

But I agree in general: as long as "param1" does not influence the application protocol parsing, the app protocol could do (any further) parametrization/negotiation itself and no WS subprotocol level negotiation is necessary.

/Tobias

v2.23.0 | Report a Bug | By Email