I like it: it makes the existence and the name of the default cache explicit to the user, with no practical drawbacks.

Thanks,
Sanne


On 10 November 2016 at 08:38, Tristan Tarrant <ttarrant@redhat.com> wrote:
In the discussion for [1] the subject of the default cache and the way
it affects configuration inheritance came up.

My proposal is:
- remove the default cache as a special cache altogether
- CacheManager.getCache()  should return the named cache specified as
default in the configuration.
- the programmatic GlobalConfigurationBuilder/GlobalConfiguration should
have the notion of the default named cache (currently this is handled in
the parser)
- Retrieving the cache named "___defaultcache" should actually retrieve
the above named cache

Opinions ?

Tristan

[1] https://github.com/infinispan/infinispan/pull/4631
--
Tristan Tarrant
Infinispan Lead
JBoss, a division of Red Hat
_______________________________________________
infinispan-dev mailing list
infinispan-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev