<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 26, 2014 at 4:58 PM, Tristan Tarrant <span dir="ltr"><<a href="mailto:ttarrant@redhat.com" target="_blank">ttarrant@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On 26/08/14 15:50, Dan Berindei wrote:<br>
><br>
> The cluster registry also uses a clustered cache, how would we ship<br>
> the cache configuration around for that cache?<br>
</div>Currently the configuration for the cluster registry is static, so there<br>
isn't any need to propagate it. My reasoning obviously falls over when<br>
we want to add some configuration to it, such as persistence.<br></blockquote><div><br></div><div>Right, I was certain we already allowed the user to override the cluster registry cache config.</div><div><br></div><div>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 :)</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>><br>
> The cluster registry is also too limited to do this check ATM, as it<br>
> doesn't support conditional operations. I'm not sure whether that's<br>
> because they just weren't needed, or it's an intentional limitation.<br>
><br>
</div>I think it was just laziness.<br>
<div><div><br>
Tristan<br>
<br>
_______________________________________________<br>
infinispan-dev mailing list<br>
<a href="mailto:infinispan-dev@lists.jboss.org" target="_blank">infinispan-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/infinispan-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a><br>
</div></div></blockquote></div><br></div></div>