Re: Why the Web needs to change

Piglet (
Thu, 31 Mar 1994 19:39:09 --100

This is an outline of and comments on replies I have


> From: Marc Andreessen <>
> Message-Id: <199403301018.KAA11229@threejane>
> Date: Wed, 30 Mar 1994 10:18:02 GMT
> The IETF URI group has been working for decades on defining such a
> beast -- the URN (Uniform Resource Name). It's currently expected by
> the year 2009.


> From: "Peter Lister, Cranfield Computer Centre" <>
> Message-Id: <>
> Date: Wed, 30 Mar 94 11:35:59 BST
> You just described URNs and local caching. URNs are not by any means unique to
> WWW in any case and are discussed separately by; don't
> underestimate the scale of the issues.

How do I subscribe to uri@bunyipcom ??
> Local caching is happening now - there is a UK cache at

It may well be, but what's the point unless my client know about it?
My argument is that my client ALWAYS BUT ALWAYS asks its `local'
server for the document, and that server responds with an uptodate
copy, be it locally cached, `area'ly cached, or from the source.


> From: "Roy T. Fielding" <>
> Message-Id: <>
> Date: Wed, 30 Mar 1994 08:15:49 -0800
> So, to make a long story short, you want hierarchical, caching proxy
> servers that use location-independent URNs. Join the crowd ;-)
> Actually, I think you will find that URNs are only useful when the
> document is a fixed standard, such as an Internet RFC, or externally-
> published book, but that is an even longer story.

I disagree. That's the whole point of checking to see if the
document is uptodate. In fact, I am quite willing for the URL to be
the URN, just that the way the client gets the document be different.

> I suggest looking at the hypertext archive of this mailing list
> at <>
> and reading all the threads on caching, forwarding cache requests,
> and URNs. This is going to take a while, but it's the only way to
> find out what's already been discussed.

I've looked here, and couldn't find much... maybe I'm looking for the
wrong keywords... any suggestions?

Timothy Hunt

<a href="">About
<a href="">About his department</a>