# Re: URCs and URL resolution

rdaniel@acl.lanl.gov
Wed, 28 Sep 94 12:19:00 -0600

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Michael Mealling: "Re: URCs and URL resolution"
- Previous message: Reed Wade: "URCs and URL resolution"
- In reply to: Reed Wade: "URCs and URL resolution"
- Next in thread: Keith Moore: "Re: URCs and URL resolution"
- Reply: Keith Moore: "Re: URCs and URL resolution"

    Message-Id: <199409281819.MAA29478@idaknow.acl.lanl.gov>

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

    Subject: Re: URCs and URL resolution

    In-Reply-To: Your message of "Wed, 28 Sep 94 10:43:39 EDT."

                 <9409281443.AA16231@honk.cs.utk.edu>

    Date: Wed, 28 Sep 94 12:19:00 -0600

    From: rdaniel@acl.lanl.gov

> 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.

Reed,

I guess I don't see these as seperate. URLs will be part of
the URC. It will be possible (if the URC server administrator
allows it) to launch a general query against the contents of
a URC server. The URN->URL resolution will be the most common
query. The service, the servers, and the browsers should be
optimized for that common case.

Ron

- Next message: Michael Mealling: "Re: URCs and URL resolution"
- Previous message: Reed Wade: "URCs and URL resolution"
- In reply to: Reed Wade: "URCs and URL resolution"
- Next in thread: Keith Moore: "Re: URCs and URL resolution"
- Reply: Keith Moore: "Re: URCs and URL resolution"