Ian Cooper wrote:
> Do we really mean (in our own language) that transparent means
> *network* transparent, or do we mean content consumer transparent?
My personal definitions:
"transparent proxy" is a proxy that the end user does not need to care
about or be aware of. It by itself does not define how this is acheived
(network redirection, WPAD or whatever automatic means, possibly
including administrative enforced proxy settings the user can't bypass).
It is not neccesary semantically transparent, only the perceieved user
experience is transparent.
"network transparent proxy" is a proxy intercepting TCP traffic.
"fully network transparent proxy" is a proxy intercepting TCP traffic
without hiding the client identity.
"semantically transparent cache" is the HTTP/1.1 definition of
"semantically transparent".
"semantically correct cache" guarantees that the user never receives
older data than he already has seen, and that proper expiry rules and
cache invalidations are in place for the cache as a whole (not only at
one node in a cache mesh)
"semantically transparent proxy" is a proxy which does not change what
the user requests or receives. No request or header rewriting is
performed, or protocol down/upgrading. I have not defined how/if caching
fits in a "semantically transparent proxy". This is probably close to
the HTTP/1.1 definition of "transparent proxy".
"non-transparent proxy" is a proxy changing the requests or content.
(same as HTTP/1.1 definition)
I do not differentiate between a proxy and it's function proxying.
-- Henrik Nordstrom Spare time Squid hacker
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST