Re: [hybi] [Uri-review] ws: and wss: schemes

David Booth <david@dbooth.org> Mon, 10 August 2009 02:05 UTC

Return-Path: <david@dbooth.org>
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 0557E3A6CFE for <hybi@core3.amsl.com>; Sun, 9 Aug 2009 19:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 NChTm8QDFOrw for <hybi@core3.amsl.com>; Sun, 9 Aug 2009 19:05:10 -0700 (PDT)
Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by core3.amsl.com (Postfix) with SMTP id 01C753A6929 for <hybi@ietf.org>; Sun, 9 Aug 2009 19:05:09 -0700 (PDT)
Received: (qmail 8095 invoked from network); 10 Aug 2009 02:05:12 -0000
Received: from 209.6.102.232 (HELO ?192.168.7.6?) (209.6.102.232) by relay01.pair.com with SMTP; 10 Aug 2009 02:05:12 -0000
X-pair-Authenticated: 209.197.102.232
From: David Booth <david@dbooth.org>
To: Jamie Lokier <jamie@shareable.org>
In-Reply-To: <20090808223414.GA20199@shareable.org>
References: <Pine.LNX.4.62.0908070531430.28566@hixie.dreamhostps.com> <1249651007.25446.8934.camel@dbooth-laptop> <Pine.LNX.4.62.0908071940050.28566@hixie.dreamhostps.com> <20090808223414.GA20199@shareable.org>
Content-Type: text/plain
Date: Sun, 09 Aug 2009 22:05:12 -0400
Message-Id: <1249869912.20315.403.camel@dbooth-laptop>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.1
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Tue, 11 Aug 2009 16:15:07 -0700
Cc: uri-review@ietf.org, hybi@ietf.org, uri@w3.org
Subject: Re: [hybi] [Uri-review] ws: and wss: schemes
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: Mon, 10 Aug 2009 02:05:11 -0000

On Sat, 2009-08-08 at 23:34 +0100, Jamie Lokier wrote:
> Ian Hickson wrote:
> > On Fri, 7 Aug 2009, David Booth wrote:
> > >
> > > This looks to me like a perfect example of a case where a new scheme is
> > > not needed, as the same thing can be accomplished by defining an http
> > > URI prefix, as described in "Converting New URI Schemes or URN
> > > Sub-Schemes to HTTP":
> > > http://dbooth.org/2006/urn2http/
> > > Note that I am talking about the *scheme*, not the protocol.  In
> > > essence, a URI prefix such as "http://wss.example/" can be defined that
> > > would serve the same purpose as a "wss:" scheme: an agent that
> > > recognizes this prefix will know to attempt the WSS protocol.  But an
> > > agent that doesn't *might* still be able to fall back to doing something
> > > useful with the URI if it were an http URI, whereas it couldn't if it
> > > were a "wss:" URI.
> > 
> > This is only expected to be used from a WebSocket API call. What fallback 
> > behaviour did you have in mind?
> 
> Tunnelling WebSocket two-way communications over standard HTTP
> messages, using any of the methods used for that, would be natural and
> probably useful behaviour.

Sounds like a good idea to me, and an excellent reason to use an http
prefix instead of a new scheme.



-- 
David Booth, Ph.D.
Cleveland Clinic (contractor)

Opinions expressed herein are those of the author and do not necessarily
reflect those of Cleveland Clinic.