# Re: Stab in the dark

Keith Moore (moore@cs.utk.edu)
Wed, 16 Mar 1994 23:12:31 -0500

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Martin Hamilton: "Stab in the dark"
- Previous message: Keith Moore: "Re: Stab in the dark"
- In reply to: Martin Hamilton: "Stab in the dark"
- Next in thread: Jon P. Knight: "Re: Stab in the dark"
- Reply: Jon P. Knight: "Re: Stab in the dark"

    Message-Id: <199403170412.XAA01188@wilma.cs.utk.edu>

    From: Keith Moore <moore@cs.utk.edu>

    To: Martin Hamilton <M.T.Hamilton@lut.ac.uk>

    Subject: Re: Stab in the dark

    In-Reply-To: Your message of "Wed, 16 Mar 1994 23:18:45 GMT."

                 <199403162318.XAA08797@lust.mrrl.lut.ac.uk>

    Date: Wed, 16 Mar 1994 23:12:31 -0500

> The attached code is a very rough sketch of a possible solution to
> the URN->UR*->URL scenario which relies on the DNS, HTTP and HTML.
> I'm not suggesting this is The Answer as far as URNs are concerned.
> An Answer, perhaps? :-)

it's okay as a proof-of-concept. I don't think it's quite ready
for production, yet, though.

> In attempting to resolve a URN of the form
>
> urn://urn.mrrl.lut.ac.uk/martin/top
>
> it does a DNS TXT lookup on the domain component, e.g.
>
> urn.mrrl.lut.ac.uk. 86400 TXT http://www.mrrl.lut.ac.uk/urn
>
> Because I'm lazy, the first http URL returned is taken as the URL
> of the server which is willing to perform the URN resolution.

certainly you'd want the client to be able to pick more intelligently
(trying other servers if attempts to use the first one failed, and
perhaps attempting to locate a nearby server first)

> Then
> the rest of the URN is appended - in the example this gives us
>
> http://www.mrrl.lut.ac

- Next message: Martin Hamilton: "Stab in the dark"
- Previous message: Keith Moore: "Re: Stab in the dark"
- In reply to: Martin Hamilton: "Stab in the dark"
- Next in thread: Jon P. Knight: "Re: Stab in the dark"
- Reply: Jon P. Knight: "Re: Stab in the dark"