When you say "client" side A and "server" side B, do you mean A is a client of server B, both using JCS (in remote cache mode) ?
If so, when B synchronizes with the remote cache, the corresponding cache items are flushed from A, so the client will never hold data not relevant to it. Hanson Char On 5/11/05, Hariprasath Manivannan <[EMAIL PROTECTED]> wrote: > Hi, > > I am planning to use the remote cache feature of JCS in my J2EE based > application. Basically my core application is a static data-store. Since the > data is static, I decided to use the remote cache feature as this can reduce > the RMI calls and network traffic. > > Now if I have a cache and both server side and client side, then I may face > issue during the remote caches synchronization. The server side cache will > be a global cache containing all the cached objects. This is fine. But once > synchronization is complete, the client cache's will become similar in > content to the server side cache. So for any given client application cache > will be holding data which is not relevant to that application. > > Is there any way where by I still maintain the remote cache, but synchronize > with primary cache server "selectively" - based on a application ID or > something like that. > > Regards, > Hari > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
