On Tue, Aug 26, 2014 at 4:58 PM, Tristan Tarrant <ttarrant@redhat.com> wrote:
On 26/08/14 15:50, Dan Berindei wrote:
>
> The cluster registry also uses a clustered cache, how would we ship
> the cache configuration around for that cache?
Currently the configuration for the cluster registry is static, so there
isn't any need to propagate it. My reasoning obviously falls over when
we want to add some configuration to it, such as persistence.

Right, I was certain we already allowed the user to override the cluster registry cache config.

Still, even if the configuration is static, I'm not a fan of adding yet another special case for the cluster registry cache. So I'm not completely sold on your idea yet :)
 
>
> The cluster registry is also too limited to do this check ATM, as it
> doesn't support conditional operations. I'm not sure whether that's
> because they just weren't needed, or it's an intentional limitation.
>
I think it was just laziness.

Tristan

_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev