On Fri, 10 Sep 1999 12:23:38 +1000, Markus Buchhorn wrote:
>
>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.
Well, there might be. It would depend on what type of error.
> And there's also the question of permission/time - being
>allowed to cache a response (Pragma: No-Cache; Expires: Now).
Doesn't that come under the catch-all term "cacheable"?
>>> 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.
Not necessarily. By taking load off the origin server you may well
enhance the performance as seen by the end-user. I know what you're
saying though.
>>> 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").
"Intercepts" seems to hint at the wrong thing (as you say).
"terminates" is probably too strong, although the request stream _is_
being terminated for cached content.
Ian
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:27 MST