Hi Dimuthu, For in-memory you need it anyway, but even for Infinispan for example.
That's to maintain references of the Cache itself. We have more than one named cache in Carbon. For example, one for registry resources, one for UM etc. This gives better performance, since not everything is cached in a single map. Now, fetching a new cache from a cache manager requires fair amount of initialization overhead, which is why this was maintained in-memory. I think you'll still need that. Thanks, Senaka. On Sat, Feb 4, 2012 at 12:47 PM, Dimuthu Leelarathne <[email protected]>wrote: > Hi Senaka, > > I see a hashmap like this in InfinispanCacheManager. > > private final Map<String, Cache> caches = > Collections.synchronizedMap(new HashMap<String, Cache>()); > > I think this code comes from InMemoryCacheManager and I don't see real > purpose of it. I am going to remove it. WDYT? > > thanks, > dimuthu > > > -- > Dimuthu Leelarathne > Technical Lead > > WSO2, Inc. (http://wso2.com) > email: [email protected] > > Lean . Enterprise . Middleware > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
