some suggestions..
In a previous episode Ian Cooper said...
::
:: proxy
:: An intermediary system which acts as both a server and a
:: client for the purpose of making requests on behalf of
:: other clients. Requests are serviced internally or by
:: passing them on, with possible translation, to other
:: servers. A proxy MUST implement both the client and server
:: requirements of this specification. A "transparent proxy"
:: is a proxy that does not modify the request or response
:: beyond what is required for proxy authentication and
:: identification. A "non-transparent proxy" is a proxy that
:: modifies the request or response in order to provide some
:: added service to the user agent, such as group annotation
:: services, media type transformation, protocol reduction,
:: or anonymity filtering. Except where either transparent or
:: non-transparent behavior is explicitly stated, the HTTP
:: proxy requirements apply to both types of proxies.
since this is the introduction of [non-]transparent perhaps a line
like: "HTTP defines [non-]transparent as above, but industry usage
typically carries different semantics as described below. Further
unspecified references to transparency in this document fit with
{HTTP|industry} usage."
::
:: cache
:: A program's local store of response messages and the
:: subsystem that controls its message storage, retrieval, and
:: deletion. A cache stores cacheable responses in order to
:: reduce the response time and network bandwidth consumption
:: on future, equivalent requests. Any client or server may
'equivalent requests' is a problem.. consider Accept headers and q
values and their interactions with proxies.. a proxy may very well
choose to give the same response back to two subsequent requests that
would have generated different variants if presented directly to the
origin server.
::
:: transparent proxy (additional definition)
:: the term "transparent proxy" is defined in [6] (and quoted
:: above). However, in the realm of Web caching, this has
:: come to define a proxy which receives traffic as a result
:: of network traffic interception. The term typically
:: describes the use of a proxy and the additional systems
:: which performing network traffic interception. The use of
:: the proxy is transparent to the client.
if we're going to describe the motivations of including cache (reduce
latency, save badwidth, increase availability..) we should probably
include the motivation for transparent proxies too: no need for client
configuration (auto or otherwise).
-P
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST