From: ccoprmm@oit.gatech.edu (Michael Mealling)
Message-Id: <199402190201.AA29031@oit.gatech.edu>
Subject: Re: caching
To: atotic@ncsa.uiuc.edu (Alexsander Totic)
Date: Fri, 18 Feb 94 21:01:07 EST
In-Reply-To: <9402181639.AA15570@void.ncsa.uiuc.edu>; from "Alexsander Totic" at Feb 18, 94 10:39 am
Alexsander Totic said this:
> 2) Browsing. I am using a WWW paradigm here.
Just to illustrate how I see things wrt URCs I'm going to change this
illustration slightly:
/URC+format\
user clicks on a link->URN->|URC+format|->user/client picks one->doc
\URC+format/
> In this scenario, user is interested in few things: he should
> be able to display the document, and speed, speed, speed.
> I beleive that client should be able to make a choice for the
> user about what URL should be retreived, because naive user does not
> have the knowledge needed to make the right decision (he does not
> know the network topology and addressing very well). If the user
> is interested in finding more about the resource, he can get
> the URC, and find more info.
But, when the URN is resolved and we get back a URC instead of just a URL
we get several important things:
1) link information (e.g. size, format, etc....)
2) TTL
3) x numbers of URLs so we can make a choice as to the URL.
I don't think we're saying anything different because in that illustration
what you have listed as several URLs is what I call a URC.
I'm thinking more and more that URN->URL resolving should be
URN->URC resolving...
-MM
-- ------------------------------------------------------------------------------ Michael Mealling ! Hypermedia WWW, WAIS, and gopher will be Georgia Institute of Technology ! here soon via MIME. Your view of the Michael.Mealling@oit.gatech.edu ! internet is about to change completely!