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

Julian Reschke <julian.reschke@gmx.de> Sun, 09 August 2009 08:04 UTC

Return-Path: <julian.reschke@gmx.de>
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 E99783A6B83 for <hybi@core3.amsl.com>; Sun, 9 Aug 2009 01:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.777
X-Spam-Level:
X-Spam-Status: No, score=-4.777 tagged_above=-999 required=5 tests=[AWL=-2.178, 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 7ZMFk5FroGBl for <hybi@core3.amsl.com>; Sun, 9 Aug 2009 01:04:58 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 5078D3A6B7F for <hybi@ietf.org>; Sun, 9 Aug 2009 01:04:58 -0700 (PDT)
Received: (qmail invoked by alias); 09 Aug 2009 07:58:19 -0000
Received: from p508FD852.dip.t-dialin.net (EHLO [192.168.178.33]) [80.143.216.82] by mail.gmx.net (mp053) with SMTP; 09 Aug 2009 09:58:19 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19SMsdDdp5SAnNa8gmhww2x/QAPGvcX+a/JvQJDpP GxkCV84IVpaZze
Message-ID: <4A7E8192.6040404@gmx.de>
Date: Sun, 09 Aug 2009 09:58:10 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.0.4) Gecko/20060516 Thunderbird/1.5.0.4 Mnenhy/0.7.4.666
MIME-Version: 1.0
To: Ian Hickson <ian@hixie.ch>
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>
In-Reply-To: <Pine.LNX.4.62.0908071940050.28566@hixie.dreamhostps.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.62
Cc: uri-review@ietf.org, hybi@ietf.org, uri@w3.org, David Booth <david@dbooth.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: Sun, 09 Aug 2009 08:04:59 -0000

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?

Are you saying the URI scheme is *only* needed within WebSocket's API? 
Why do you need a URI scheme in the first place, then?

BR, Julian