--- On Fri, 8/14/09, Jeffrey Kesselman <jef...@gmail.com> wrote:
> From: Jeffrey Kesselman <jef...@gmail.com> > Subject: Okay next tqo quick questions... > To: "JCS Users List" <jcs-users@jakarta.apache.org> > Date: Friday, August 14, 2009, 3:55 PM > (1) Why does CacheAccess.get() > return an Object and not a Serializable. > Doesn't any object stored in the cache have to be a > Serializable? > The original ICacheAccess interface take and returns objects. The idea was that the cache should be usable with just memory auxiliaries. So we shouldn't restrict to Serializable. However, nearly every other auxiliary requires it. . . . > (2) If i call get(...) on my remote cache and the object > isnt there, it will > attempt to fetch iot from its server yes? is there > some way for me to know > this is happening? some kind of .contains(...) call I could > call first or > something? > You call get on a local cache. It it is not present locally, the remote cache client will call get on the remote cache server. If the server doesn't have it, it will do the same thing. If the server is configured with a failover, it will call get on the failover. You don't have anyway to know before calling get what will happen underneath. What would the contains method do? I don't understand. Aaron > -- > ~~ Microsoft help desk says: reply hazy, ask again later. > ~~ > --------------------------------------------------------------------- To unsubscribe, e-mail: jcs-users-unsubscr...@jakarta.apache.org For additional commands, e-mail: jcs-users-h...@jakarta.apache.org
