Re: Taxonomy Term closure needed

From: Markus Buchhorn (markus@acsys.anu.edu.au)
Date: Thu Sep 09 1999 - 20:23:38 MDT


At 17:40 9/09/99 -0700, Joe Touch wrote:
>A cache is a system which stores temporary copies of response messages,
>and replays them when prompted.

 .. of successful response messages..? or somesuch - not much point caching
error results. And there's also the question of permission/time - being
allowed to cache a response (Pragma: No-Cache; Expires: Now).

>> Reverse Proxy
>
>This is the one I find odd. There is nothing reverse about it.
>It's just a proxy cache co-located (or nearly-colocated) with the server.
>
>Why not just call it a "server-side, or server-proximal" cache?

Agreed. A 'server-side' cache is designed to take load off the origin
server, but does nothing for the network or performance as seen by the
end-user. A 'network' cache is designed to speed up responses for the
end-user and reduce network load.

The term 'Reverse Proxy' to me sounds like a pre-populated caching proxy...

>> Second Derivative Terms: (Build upon first derivative terms)
>> Caching Proxy
>> A new defintion. Editors View - Consensus
>> "A proxy with a cache, acting as server to clients, and
>> a client to servers"
>
>And which intercepts requests that have associated responses
>in its cache.

No - it "intercepts" _all_ requests, but if it can't service them will
forward them on on behalf of the client, and store the response while also
passing it on. And depending on the application it may not be an
"intercept" (which sounds like a hijack) it may be a deliberate direct
request ("have you got this? If not please get it for me").

>> Replica Origin Server
>> New definition. Editors View - Open Disussion
>> Editors-Note: In light of the recent disuccsion, the authoritative
>> attribute is quiestionable.
>> "origin server storing a persistent replica of a data set
>> stored at the authoritative reference"

How is this different to a mirror ?

>> Surrogate Cache
>> Not Defined. Editors View - Needs Discussion
>> Editors-Node: Do we need it, or is it a role that is provided by
proxies,
>> reverse proxies and replica origin servers?

What does it actually do? If it replaces the role of an existing cache
(dynamically or otherwise) it sounds like a cache-sibling or peer?

Cheers,
        Markus

Markus Buchhorn, Advanced Computational Systems CRC | Ph: +61 2 62798810
email: markus@acsys.anu.edu.au, snail: ACSys, RSISE Bldg,|Fax: +61 2 62798602
Australian National University, Canberra 0200, Australia |Mobile: 0417 281429



This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:27 MST