jakarta-jcs-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Travis Savo <ts...@IFILM.com>
Subject RE: diff between Remote Cache and Lateral TCP Cache
Date Sat, 19 Jun 2004 00:35:02 GMT
The objective is to have a distributed index. If you put locally from a
lateral get, your duplicating the index. Lateraling allows you to have an
index that's divided among the caches, yet still appears as one big index to
any given client. Whoever gets the object first is the owner of the index,
which is (in theory) not in any other cache, yet still accessible by all
caches.

Weather or not this is a Good Thing(tm) depends on your usage
characteristics.

-Travis Savo <tsavo@ifilm.com>

-----Original Message-----
From: Hanson Char [mailto:hanson_char@yahoo.com]
Sent: Friday, June 18, 2004 3:41 PM
To: 'Turbine JCS Users List'
Subject: RE: diff between Remote Cache and Lateral TCP Cache



>Lateral cache treats all caches as peers. When a cache gets a cache miss,
it asks all the other caches if they have the object in question.
>If one of them responds, the object is returned as a cache hit, but IS NOT
stored locally

Out of curiosity, why is an object obtained from the lateral peers not
stored locally (which would speed up subsequent local access) ?  I mean
what's the rationale behind this design ?

Hanson


---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-jcs-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-jcs-user-help@jakarta.apache.org


Mime
View raw message