> > From fberzau@novell.com Thu Sep 9 19:50 EDT 1999
> >
> > Here's a suggestion for definitions of both forward cache
> > and reverse cache:
> >
> > A FORWARD CACHE is a cache operating on behalf of a
> > user agent. It is typically outside the control of any
> > content provider. It is the responsibility of the client or
> > network operators to deliver requests to the forward cache.
> > Origin servers are typically oblivious to the existence of
> > forward caches - a forward cache looks just like another client
> > to them, with the exception of a special HTTP request header that
> > some forward caches insert.
> >
> > A REVERSE CACHE is the cache operating on behalf of a
> > origin server. It is typically controlled by a content provider.
> > It is the responsibility of the content provider to deliver requests
> > to the reverse cache. Clients are oblivious to the existence of
> > reverse caches - a reverse cache looks just like the origin server
> > to them, with the exception of a special HTTP response header
> > that some reverse caches insert.
> >
> > Frank
There is no such thing as "on behalf of" in proxies.
They cache things they get, and serve them to requests they receive.
These definitions are dependent on who pays for it,
who controls it, etc.
And whether they're oblivious to them or not is
implementation dependent.
The use of forward/reverse still isn't justified.
Joe
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:27 MST