Re: [hybi] WebSocket sub protocol name.

Greg Wilkins <gregw@webtide.com> Sat, 19 December 2009 00:32 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 8EDA13A635F for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 16:32:07 -0800 (PST)
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 ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RwrD5vzVLwF1 for <hybi@core3.amsl.com>; Fri, 18 Dec 2009 16:32:06 -0800 (PST)
Received: from mail-yw0-f185.google.com (mail-yw0-f185.google.com [209.85.211.185]) by core3.amsl.com (Postfix) with ESMTP id 889383A682F for <hybi@ietf.org>; Fri, 18 Dec 2009 16:32:06 -0800 (PST)
Received: by ywh15 with SMTP id 15so3870038ywh.5 for <hybi@ietf.org>; Fri, 18 Dec 2009 16:31:48 -0800 (PST)
Received: by 10.100.50.24 with SMTP id x24mr7563256anx.51.1261182708675; Fri, 18 Dec 2009 16:31:48 -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 16sm1749538gxk.11.2009.12.18.16.31.44 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 18 Dec 2009 16:31:47 -0800 (PST)
Message-ID: <4B2C1EE4.2080806@webtide.com>
Date: Sat, 19 Dec 2009 11:31:32 +1100
From: Greg Wilkins <gregw@webtide.com>
User-Agent: Thunderbird 2.0.0.23 (X11/20090817)
MIME-Version: 1.0
To: "\"Fumitoshi Ukai (????)\"" <ukai@chromium.org>
References: <de17d48e0912062058u72db7455x4e211cb05da19070@mail.gmail.com>
In-Reply-To: <de17d48e0912062058u72db7455x4e211cb05da19070@mail.gmail.com>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: whatwg@lists.whatwg.org, hybi@ietf.org
Subject: Re: [hybi] WebSocket sub protocol name.
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: Sat, 19 Dec 2009 00:32:07 -0000

Wow - what a thread about such a simple concept as a name!!!!

But to inject a lateral thought.   I think the protocol name
should be a URL (kind of in the same way that DTD's and style sheets
are specified by URI).

Otherwise we are going to have problems with uniqueness and allocation
of protocol names - and will have to have central authorities policing
them etc.

If we make it a URL, then we have uniqueness and the URL can point
to a webpage that describes the protocol.

cheers