On Mon, 23 Aug 1999, Patrick McManus wrote:
> I work with one of these.. two physical locations where the
> applications share an Oracle Database in Replicated Server Mode
> (rw).. I'd call that a replica as neither of the sites is
> authoritative in any manner.
How will you servers serving the same content for the same URI, just with
different IPs? It is more than just a "replica", it should be a clone, but
maybe that's not needed.
> on the cache vs mirror thing:
> in my mind the difference between a cache and a mirror is that in the
> cache scenario the cache is responsible for enforcing expiration
> information (do I serve my copy or do I get one from the origin
> server?), and in the mirror scenario the origin server is responsible
> for changing the mirror's copy when appropriate, the mirror never
> makes an expiration decision.
A replica should server the same object, a cache will serve only a cached
view of this object (an HTTP view for instance). For files it is the same,
but not for other kind of contents.
Joe said that caches are serving temporary thing, but you may
thing of a ridiculously long expiration date and many hits, and the
resource will stay forever in the cache, so I don't think that time is an
issue there.
~~Yves
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST