# Re: DNS lookups for URLs (was: URN functionality from URLs)

Josh Osborne (stripes@uunet.uu.net)
Wed, 15 Dec 1993 11:14:43 -0500 (EST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Alexander Dupuy: "Re: DNS lookups for URLs (was: URN functionality from URLs)"
- Previous message: Tim Berners-Lee: "Re: URN functionality from URLs"
- In reply to: Larry Masinter: "Re: DNS lookups for URLs (was: URN functionality from URLs)"

    From: stripes@uunet.uu.net (Josh Osborne)

    Message-Id: <9312151614.AA18426@rodan.UU.NET>

    Subject: Re: DNS lookups for URLs (was: URN functionality from URLs)

    To: masinter@parc.xerox.com (Larry Masinter)

    Date: Wed, 15 Dec 1993 11:14:43 -0500 (EST)

    In-Reply-To: <93Dec15.003823pst.2732@golden.parc.xerox.com> from "Larry Masinter" at Dec 15, 93 00:38:17 am

[...]
>Currently, we have the situation where some URNs refer to things that
>are cachable (they refer to exact copies of bits) and other are not
>(they refer to locations that are themselves updatable).
>
>Please please try to separate these out when you're making proposals.
>Would you put the updatable resources in the cache?

The simplest answer is to only cache locations. The almost-as-simple
answer is to only cache things that have an explicit TTL, or expire date
(which HTTP is capable of providing). Other answers are left as an
exercise to the interested reader.

- Next message: Alexander Dupuy: "Re: DNS lookups for URLs (was: URN functionality from URLs)"
- Previous message: Tim Berners-Lee: "Re: URN functionality from URLs"
- In reply to: Larry Masinter: "Re: DNS lookups for URLs (was: URN functionality from URLs)"