The cache-alias stuff in WF is actually a matter of JNDI and internal
service naming. It actually returns the same CacheImpl for all aliases.
The cache manager has no idea about the alias.
Tristan
On 16/12/2015 11:26, Galder ZamarreƱo wrote:
Hey Tristan, sorry for the delay. Looks good to me.
IIRC, Paul did some kind of cache name alias work for WF clustering and I wonder if they
could potentially rely on this? The use cases might be different but worth checking up
with him.
Cheers,
--
Galder ZamarreƱo
Infinispan, Red Hat
> On 30 Nov 2015, at 20:58, Tristan Tarrant <ttarrant(a)redhat.com> wrote:
>
> Hi everybody,
>
> to address the needs of Teiid to implement materialized views on
> Infinispan caches, I have written a small design document describing
> "alias caches" [1].
> To be able to fully support the use-case in remote configurations, we
> need to perform the switching operation remotely. Since remote admin
> functionality is also required by the JCache integration code, I have
> created a separate page [2] describing what the remote admin client
> would look like in terms of functionality and packaging.
>
> As usual, comments are welcome
>
>
> [1]
https://github.com/infinispan/infinispan/wiki/Alias-Caches
> [2]
https://github.com/infinispan/infinispan/wiki/Remote-Admin-Client
> --
> Tristan Tarrant
> Infinispan Lead
> JBoss, a division of Red Hat
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev