More about it here:
http://blog.infinispan.org/2014/04/infinispan-700alpha3-is-out.html
Cheers,
--
Mircea Markus
Infinispan lead (www.infinispan.org)
___
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
More gripping than a gripping spy novel:
http://blog.infinispan.org/2014/04/infinispan-security-1-authorization.html
Fortunately you don't need a valid javax.security.auth.Subject to be
able to read it :)
Tristan
___
infinispan-dev mailing list
On 04 Apr 2014, at 19:11, William Burns mudokon...@gmail.com wrote:
On Fri, Apr 4, 2014 at 3:29 AM, Radim Vansa rva...@redhat.com wrote:
Hi,
I still don't think that the document covers properly the description of
failover.
My understanding is that client registers clustered listeners
On Fri, Apr 11, 2014 at 8:36 AM, Galder Zamarreño gal...@redhat.com wrote:
On 04 Apr 2014, at 19:11, William Burns mudokon...@gmail.com wrote:
On Fri, Apr 4, 2014 at 3:29 AM, Radim Vansa rva...@redhat.com wrote:
Hi,
I still don't think that the document covers properly the description of
OK, now I get the picture. Every time we register to a node (whether the
first time or after previous node crash), we receive all (filtered) keys
from the whole cache, along with versions. Optionally values as well.
In case that multiple modifications happen in the time window before
