Re: Deployment of new URI schemes (was Re: request for a new URL scheme)

ZB Lucas <zblucas@semaphore.com> Fri, 12 April 1996 00:58 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27864; 11 Apr 96 20:58 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27860; 11 Apr 96 20:58 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa17643; 11 Apr 96 20:58 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id UAA14451 for uri-out; Thu, 11 Apr 1996 20:37:18 -0400
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id UAA14446 for <uri@services.bunyip.com>; Thu, 11 Apr 1996 20:37:08 -0400
Received: from semaphore.semaphore.com by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA07794 (mail destined for uri@services.bunyip.com); Thu, 11 Apr 96 20:36:49 -0400
Received: (from zblucas@localhost) by semaphore.semaphore.com (8.6.12/8.6.11) id RAA00247; Thu, 11 Apr 1996 17:34:06 -0700
Date: Thu, 11 Apr 1996 17:34:06 -0700 (PDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: ZB Lucas <zblucas@semaphore.com>
X-Sender: zblucas@semaphore.semaphore.com
To: Daniel LaLiberte <liberte@ncsa.uiuc.edu>
Cc: uri@bunyip.com
Subject: Re: Deployment of new URI schemes (was Re: request for a new URL scheme)
In-Reply-To: <9604102200.AA21360@void.ncsa.uiuc.edu>
Message-Id: <Pine.SUN.3.91.960411172114.217A-100000@semaphore.semaphore.com>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk


> Browsers should allow users to specify proxies that handle specific
> URI schemes, possibly new schemes.  Netscape, for one, still assumes
> that any URI with a scheme it does not know about is a relative
> URL, and it has no way to specify proxies to handle specific new
> schemes.   Mosaic for X has fixed these problems, partly at my
> insistence.

right now the win95 shell supports any sort of URL protocol.  if you do a 
ShellExec on a valid URL, the shell will look in the registry for a 
handler of that protocol.  and then pass it off to them.  both NS2.0 and 
MSIE take advantage of this.  it also permits apps to register themselves 
as handlers for a MIME type.

this means that a user can go to the start-run menu and enter 
"http://www.home.com" and clik OK and it will activate the correct app 
and display the desired page.

MSIE is smart enough that whenever it runs across a protocol that it 
doesnt recognize, it always does a shellexec to see if anybody on the 
system knows how to handle it. 

so if someone wanted to, they could easily implement a link like 
"mud:bestmud.com:8080" in a web page and if someone were running MSIE on 
win95 it would passed off to the mud client.  i believe there is even an 
option to pass the URL with or without the protocol prefixed.

{zeke}