Re: request for a new URL scheme

"John C. Daub" <jcd7106@tam2000.tamu.edu> Wed, 10 April 1996 20:16 UTC

Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa26531; 10 Apr 96 16:16 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa26527; 10 Apr 96 16:16 EDT
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa15119; 10 Apr 96 16:16 EDT
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id PAA22651 for uri-out; Wed, 10 Apr 1996 15:35:58 -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 PAA22646 for <uri@services.bunyip.com>; Wed, 10 Apr 1996 15:35:44 -0400
Received: from tam2000.tamu.edu by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA25814 (mail destined for uri@services.bunyip.com); Wed, 10 Apr 96 15:35:39 -0400
Received: from localhost (jcd7106@localhost) by tam2000.tamu.edu (8.7.3/8.7.3) with SMTP id OAA06483; Wed, 10 Apr 1996 14:35:03 -0500 (CDT)
Date: Wed, 10 Apr 1996 14:35:02 -0500 (CDT)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "John C. Daub" <jcd7106@tam2000.tamu.edu>
Reply-To: hsoi@tamu.edu
To: Rich Salz <rsalz@osf.org>
Cc: uri@bunyip.com
Subject: Re: request for a new URL scheme
In-Reply-To: <9604101917.AA09724@sulphur.osf.org>
Message-Id: <Pine.SOL.3.92.960410143008.2603A-100000@tam2000.tamu.edu>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

On Wed, 10 Apr 1996, Rich Salz wrote:

> I would rather see browers that allowed telnet-style helper apps to
> be specified on a per-port basis.

in other words, the current browser that you are using would have to
parse the telnet url.  based upon the the port (if any was specified,
else default to the "generic" telnet app), launch x y or z application.

that could also be pretty cool.  would allow some nice flexibility.

but as was stated sometime before, a problem with what i was
originally proposing was that the current client authors would have
to rewrite their code to support a new URL scheme.

to do something like this would require a good deal of rewriting
to be able to support all some thousand possible port numbers.
even if people could give a range of ports (e.g. ports between
4000 and 5000, use X; between 5001 and 7000 use Y, else use default),
who's to say how many possible settings one user might wnat to have
(who knows...some smart-ass might want an individual app for every
port out there....you never know).

so, how to support that without some major rewriting? :(

i think it's a good idea, and if it wouldn't cause too much dissruption
and rewriting, why not go for this also?

John C. Daub (aka Hsoi)   | <mailto:hsoi@tamu.edu>
Grad Student, Lab Manager | <http://http.tamu.edu:8000/~jcd7106/>
Self-proclaimed Mac Guru  | Department of Speech Communication
Will program for food.    | Texas A&M University, USA