Re: [hybi] How to select which websocket protocol to use

Greg Wilkins <gregw@webtide.com> Wed, 23 December 2009 00:36 UTC

Return-Path: <gregw@webtide.com>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A4FC73A68C6 for <hybi@core3.amsl.com>; Tue, 22 Dec 2009 16:36:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.534
X-Spam-Level:
X-Spam-Status: No, score=-2.534 tagged_above=-999 required=5 tests=[AWL=0.065, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3v3PUG7EjSmZ for <hybi@core3.amsl.com>; Tue, 22 Dec 2009 16:36:40 -0800 (PST)
Received: from mail-gx0-f228.google.com (mail-gx0-f228.google.com [209.85.217.228]) by core3.amsl.com (Postfix) with ESMTP id C8A803A6452 for <hybi@ietf.org>; Tue, 22 Dec 2009 16:36:39 -0800 (PST)
Received: by gxk28 with SMTP id 28so639128gxk.9 for <hybi@ietf.org>; Tue, 22 Dec 2009 16:36:20 -0800 (PST)
Received: by 10.90.17.31 with SMTP id 31mr256591agq.2.1261528580318; Tue, 22 Dec 2009 16:36:20 -0800 (PST)
Received: from ?10.10.1.11? (60-242-119-126.tpgi.com.au [60.242.119.126]) by mx.google.com with ESMTPS id 14sm3613825gxk.14.2009.12.22.16.36.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 22 Dec 2009 16:36:19 -0800 (PST)
Message-ID: <4B3165EE.6040308@webtide.com>
Date: Wed, 23 Dec 2009 11:35:58 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: Francis Brosnan Blazquez <francis@aspl.es>
References: <1261492671.8667.755.camel@vulcan.aspl.local>
In-Reply-To: <1261492671.8667.755.camel@vulcan.aspl.local>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: WhatWG <whatwg@whatwg.org>, Hybi <hybi@ietf.org>
Subject: Re: [hybi] How to select which websocket protocol to use
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 23 Dec 2009 00:36:40 -0000

Francis Brosnan Blazquez wrote:
> Hi,
> 
> In the case someone wants to use BWTP, how is this signaled to the
> Websocket (javascript) API? Is this controlled by the "protocol"
> constructor argument?

I believe that is the intent.

However, for this to work well, I think there needs to be several
other "systems" put in place.

To avoid protocol name clashes, either they will need to be allocated
by IANA or something already unique like URLs will need to be used.

I would also like to see that the usage of the frame-type bytes
be scoped by protocol name.   So that if a protocol like BWTP
wants to define a set of frametypes (for header frames vs
body frames etc.), then it can do so with out clashing with
other uses of those bytes.    This would also avoid the need
for IANA to allocated additional values for this byte.


cheers