>As for the distinction between caching and replication, I define
>caching as creating a copy of an object at a point that would see
>requests for the object regardless of whether or not it has a copy.
>Examples: main memory cache on the browser, a proxy cache,
>main memory cache at the server. That is, caching creates copies
>along the normal path of request and data flow.
Normal path for a request needs to be clarified :
For instance transparent caching modifies the normal path of a request.
Also, when using ICP with siblings, the request may be redirected to a
sibling cache
containing the requested URL, thus modifying the normal path.
I'd rather say that the final destination of the request is not modified
with a caching system (considering that a cache mesh acts as a virtual
unique cache from the origin request point of view) , while a replication
system changes the final destination .
>Replication, on the other hand is creating a copy of an object at
>a place that would not normally see any requests for this object.
>Thus, requests must take a detour to get to this place.
Agreed.
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:26 MST