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

Erik Wilde <dret@berkeley.edu> Thu, 20 August 2009 01:44 UTC

Return-Path: <dret@berkeley.edu>
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 BE2A33A6C87 for <hybi@core3.amsl.com>; Wed, 19 Aug 2009 18:44:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 CTi4wlWHY53a for <hybi@core3.amsl.com>; Wed, 19 Aug 2009 18:44:56 -0700 (PDT)
Received: from smtp.ischool.berkeley.edu (bliss.ISchool.Berkeley.EDU [128.32.78.13]) by core3.amsl.com (Postfix) with ESMTP id 2700F28C120 for <hybi@ietf.org>; Wed, 19 Aug 2009 18:44:19 -0700 (PDT)
Received: from [128.32.226.216] (dhcp216.ISchool.Berkeley.EDU [128.32.226.216]) (authenticated bits=0) by smtp.ischool.berkeley.edu (8.13.1/8.13.1) with ESMTP id n7K1iKNA011699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 19 Aug 2009 18:44:20 -0700
Message-ID: <4A8CAA72.3000209@berkeley.edu>
Date: Wed, 19 Aug 2009 18:44:18 -0700
From: Erik Wilde <dret@berkeley.edu>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>
References: <OF22CD1320.96C55266-ON85257610.004AB599-85257610.004BC9CA@lotus.com> <C9931C12-E123-437D-8E7D-F8C680C62397@mnot.net>
In-Reply-To: <C9931C12-E123-437D-8E7D-F8C680C62397@mnot.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.67 on 128.32.78.13
Cc: URI <uri@w3.org>, hybi@ietf.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: Thu, 20 Aug 2009 01:44:57 -0000

hello mark.

Mark Nottingham wrote:
> I can't help but feel that if we follow the arguments given in this 
> thread, there won't be any need for FTP, or telnet, or any other URI 
> schemes; all will be subsumed by HTTP, and eventually we won't need any 
> URI schemes at all (because it's HTTP all the way down).

http://dret.typepad.com/dretblog/2009/07/the-last-uri-scheme-youll-ever-need.html 
was something i wrote recently based on another instance where people 
were arguing that from now on, all we'll ever need is HTTP URIs and 
string matching to detect special classes of URIs, that can then be 
handled differently, if an application has knowledge of the pattern that 
needs to be matched.

while the argument for string matching for "special URIs" has been 
repeated a number of times, i still haven't seen any example in real 
life where this happened in the way predicted: plain HTTP users 
discovering useful metadata or getting useful fallback behavior, and 
other applications doing string matching and implementing non-HTTP 
behavior. are there any examples where this has happened on any 
significant scale?

cheers,

dret.