# Re: caching

Randy Bush (randy@psg.com)
Wed, 16 Feb 1994 15:41:04 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Keith Moore: "Re: caching"
- Previous message: Keith Moore: "Re: Finding URN->URL servers (fwd)"
- In reply to: Michael Mealling: "Re: caching"
- Next in thread: Michael Mealling: "Re: caching"
- Reply: Michael Mealling: "Re: caching"
- Reply: Karen R. Sollins: "caching"

    Message-Id: <m0pWvrc-000306C@rip.psg.com>

    From: randy@psg.com (Randy Bush)

    Subject: Re: caching

    To: uri@bunyip.com

    Date: Wed, 16 Feb 1994 15:41:04 -0800 (PST)

    In-Reply-To: <199402161837.AA10452@oit.gatech.edu> from "Michael Mealling" at Feb 16, 94 01:37:31 pm

> Can someone please argue for why we should have some support for caching
> in the URN functional spec

The point was not support for caching. The point is that some feel that the
object which a URN names should be sufficiently stable and unique that an
entity could fetch it and hold on to it with the presumption that the object
would still be a valid referee.

The underlying issue is fairly deep and we keep mushing around it without
being explicit. What is named? A stable object, or a way to get something
which may differ from request to request?

- Next message: Keith Moore: "Re: caching"
- Previous message: Keith Moore: "Re: Finding URN->URL servers (fwd)"
- In reply to: Michael Mealling: "Re: caching"
- Next in thread: Michael Mealling: "Re: caching"
- Reply: Michael Mealling: "Re: caching"
- Reply: Karen R. Sollins: "caching"