Client-side expanded url's

Mirsad Todorovac (tm@rasips2.rasip.etf.hr)
Thu, 7 Mar 1996 09:59:35 +0100 (MET)


From: Mirsad Todorovac <tm@rasips2.rasip.etf.hr>
Message-Id: <199603070859.JAA26689@rasips2.rasip.etf.hr>
Subject: Client-side expanded url's
To: uri@bunyip.com
Date: Thu, 7 Mar 1996 09:59:35 +0100 (MET)
Cc: tm@rasips2.rasip.etf.hr (Mirsad Todorovac)


There are situations, especially in documents related to Internet and
some other areas, when you can fetch desired document from multiple sources.
The locations may differ in "net length" between client and paticular servers,
and servers may differ by their average load.

Therefore it would be of practical value to have such URL's where part of
the URL would be expanded on client, by some brosers setting or environment
variable.

Then URL would break into two parts:

	- client modifiable part with default value
	- database specific part

Eg. when we reference RFC1738, we could do it like this:

	http://{$RFC_DEP|ds.internic.net:/rfc/}rfc1738.txt

[ Now, please ignore the syntax, because it is not a part of proposal, just
a way to express desired subject. ]

This would mean:

	Get rfc1738.txt from ds.internic.net, directory /rfc/

	or from your preffered site, specified in environment variable
	WWW_RFC_DEP, which you can set to your nearest mirror.

This proposal, in contrast to URI's, requires only minor changes to
clients, and it should be considered how to deploy it into current URL
scheme, and whether it is posible to do it without breaking existing
browsers (which in that case couldn't get object even from distant, slow
site).



-- 
    | Mirsad Todorovac					|
    | Faculty of Electrical Engineering and Computing	|
    | University of Zagreb				|
    | Unska 3, Zagreb, Croatia 10000			|
    |							|
    | e-mail: mirsad.todorovac@fer.hr			|