Re: Client-side expanded url's
"Gregory J. Woodhouse" <gjw@wnetc.com> Thu, 07 March 1996 19:58 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa18760;
7 Mar 96 14:58 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa18755;
7 Mar 96 14:58 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa11833;
7 Mar 96 14:58 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id
NAA22083 for uri-out; Thu, 7 Mar 1996 13:52:14 -0500
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 NAA22072 for
<uri@services.bunyip.com>; Thu, 7 Mar 1996 13:51:07 -0500
Received: from shellx.best.com by mocha.bunyip.com with SMTP
(5.65a/IDA-1.4.2b/CC-Guru-2b)
id AA28373 (mail destined for uri@services.bunyip.com);
Thu, 7 Mar 96 13:51:04 -0500
Received: (gjw@localhost) by shellx.best.com (8.6.12/8.6.5) id KAA17694;
Thu, 7 Mar 1996 10:41:26 -0800
Date: Thu, 7 Mar 1996 10:41:26 -0800 (PST)
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Gregory J. Woodhouse" <gjw@wnetc.com>
X-Sender: gjw@shellx.best.com
To: Gary Adams - Sun Microsystems Labs BOS <Gary.Adams@east.sun.com>
Cc: uri@bunyip.com, mirsad.todorovac@fer.hr, tm@rasips2.rasip.etf.hr
Subject: Re: Client-side expanded url's
In-Reply-To: <199603071304.IAA14740@zeppo.East.Sun.COM>
Message-Id: <Pine.SGI.3.91.960307103058.15504A-100000@shellx.best.com>
X-Url: http://www.wnetc.com/
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk
It occurs to me that this could function somewhat like mail exchangers.
In the domain name system, a domain may have any number of MX records,
with eachc being given a preference. The MTA thene tries them in order.
Similarly, web UA could try the first server and if it doesn't respond
(or is too slow, whatever that means) go on to the second. Under this
scheme, my home pave would look something like
http://{www.wnetc.com,5;www.best.com/%7Egjw,10}
In this case, nothing would be gained, but it might be useful with mirror
sites, or to specify that a local copy should be used if it is available,
as it
{file://,0;http://127.0.0.1,5;http://wherever.ext}<rest of URL>
---
Gregory Woodhouse gjw@wnetc.com
home page: http://www.wnetc.com/
resource page: http://www.wnetc.com/resource/
- Client-side expanded url's Mirsad Todorovac
- Re: Client-side expanded url's Gary Adams - Sun Microsystems Labs BOS
- Re: Client-side expanded url's Gregory J. Woodhouse
- Re: Client-side expanded url's Reed Wade
- Re: Client-side expanded url's Mic Bowman