[infinispan-dev] Design of temote event handling in Hot Rod

Galder Zamarreño galder at redhat.com
Wed Feb 22 11:11:28 EST 2012


On Feb 22, 2012, at 5:10 PM, Galder Zamarreño wrote:

> 
> On Feb 22, 2012, at 2:57 PM, Manik Surtani wrote:
> 
>> 
>> On 22 Feb 2012, at 13:53, Galder Zamarreño wrote:
>> 
>>>>> 
>>>>> Client A when it receieves the notification it realises that the notification is not originated locally and can decide to delete the key from the near cache.
>>>> 
>>>> Client A and Client B are two threads in the same VM as the embedded cache with a remote cache store?
>>> 
>>> Maybe, but not necessarily. It could very easily happen that Client A and Client B are running on the same machine but in different VMs.
>> 
>> Ok, just trying to understand your use case.  So we assume Client A and Client B are different JVMs, with different Infinispan instances, but talking to the same Hot Rod servers via the RemoteCacheStore?
> 
> Yeah, for example, Client A and Client B could be two AS7 instances clustered that are running on the same machine, possibly part of a bigger cluster. Granted, if you have a cluster set betwen these two AS7 instances already, you could just cluster the near caches and avoid the need for notifications. However, I don't think the use case I hinted above seems that far fetched.

Remember as well that the suggested identification could help with performance as discussed in the other part of this thread.

> 
>> 
>> --
>> Manik Surtani
>> manik at jboss.org
>> twitter.com/maniksurtani
>> 
>> Lead, Infinispan
>> http://www.infinispan.org
>> 
>> 
>> 
>> _______________________________________________
>> infinispan-dev mailing list
>> infinispan-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/infinispan-dev
> 
> --
> Galder Zamarreño
> Sr. Software Engineer
> Infinispan, JBoss Cache
> 

--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache




More information about the infinispan-dev mailing list