> From: Ian Cooper <ian@mirror-image.com>
> To: Joe Touch <touch@ISI.EDU>
> Cc: wrec@cs.utk.edu
>
> On Thu, 9 Sep 1999 17:40:49 -0700 (PDT), Joe Touch wrote:
>
> >> Mirror
> >> Not defined. Editors View - Nees Discussion
> >> Editors-Note: An attempt at taxonomy has been made. It is clear
> >> from discussion that a definition is in order. The taxonomic variants
> >> can then be defined from it.
> >
> >Hmm - a MIRROR is a server with content identical to that of another
> >server. (?) Such equality is maintained on a periodic basis. (?)
>
> Would that limit us to an environment where www.apache.org.uk is a
> mirror for www.apache.org, but
> http://sunsite.org.uk/Mirrors/ftp.apache.com/pub/apache/ is not?
>
> "Identical" in what sense and in which direction?
Identical 'direction' would be in terms of the user.
The semantic definition of identical (same protocol, same data content)
is something we can let float (and say it's a matter of judgement
and interpretation).
> >Why not just call it a "server-side, or server-proximal" cache?
>
> I thought we agreed on this (and your issues) in Oslo?
>
> The idea was (correct me if I'm wrong) to bundle "accelerators" and
> "reverse proxies" under the same general heading and to acknowledge
> the various synonyms that are in common usage.
Sounds good to me.
> >> Caching Reverse Proxy (Accelerator)
> >> Not Defined. Editors View - Needs Discussion
> >> Editors-Note: Do we need it? Suggested definition
> >> "A reverse proxy with a cache, acting as server to clients, and
> >> a client to servers"
> >
> >A proxy cache co-lococated (or nearly-so) with a server.
> >The term "server-side or server-proximal" would be better.
>
> Hmm. Is a "caching reverse proxy" the same as a "reverse proxy"?
Dunno - can a proxy do anything besides cache? (it seems so).
In that case there could be a reverse proxy that (e.g.)
redirects, but doesn't cache.
Joe
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:27 MST