# URCs and URL resolution

Reed Wade (wade@cs.utk.edu)
Wed, 28 Sep 1994 10:43:39 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- Previous message: Erik Jul: "URCs and the world into which they are born"
- Next in thread: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- Reply: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- Reply: Michael Mealling: "Re: URCs and URL resolution"
- Maybe reply: Paul Francis: "Re: URCs and URL resolution"
- Maybe reply: Paul Francis: "Re: URCs and URL resolution"
- Maybe reply: pays@faugeres.inria.fr: "Re: URCs and URL resolution"

    Message-Id: <9409281443.AA16231@honk.cs.utk.edu>

    To: uri@bunyip.com

    Subject: URCs and URL resolution

    Date: Wed, 28 Sep 1994 10:43:39 -0400

    From: Reed Wade <wade@cs.utk.edu>

Just to put another world view out on the table-

We have envisioned URC-like information being available
in 2 ways.

One would be a full URC (or URC-like thing) with lots of
handy info which you might get via a whois++ search or
related lookup.

The other--for URL resolution would use a very lightweight
RPC or RPC-like mechanism.

(I'm trying to be conservative in my use of UR* terms because
there are a lot of divergent ideas as to what they really mean.)

Reed Wade
---------
Netlib Development Group
wade@cs.utk.edu -- http://www.netlib.org/utk/people/ReedWade.html

- Next message: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- Previous message: Erik Jul: "URCs and the world into which they are born"
- Next in thread: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- Reply: rdaniel@acl.lanl.gov: "Re: URCs and URL resolution"
- Reply: Michael Mealling: "Re: URCs and URL resolution"
- Maybe reply: Paul Francis: "Re: URCs and URL resolution"
- Maybe reply: Paul Francis: "Re: URCs and URL resolution"
- Maybe reply: pays@faugeres.inria.fr: "Re: URCs and URL resolution"