[JBoss JIRA] Created: (ISPN-1263) Allow a type safe selection of the cache used by the JCache interceptors
by Kevin Pollet (JIRA)
Allow a type safe selection of the cache used by the JCache interceptors
------------------------------------------------------------------------
Key: ISPN-1263
URL: https://issues.jboss.org/browse/ISPN-1263
Project: Infinispan
Issue Type: Feature Request
Components: CDI integration
Reporter: Kevin Pollet
Assignee: Kevin Pollet
Priority: Minor
Currently the name of the cache which will be used by the JCache interceptors has to be specified in JCache annotations (e.g {{@CacheResult(cacheName="greeting-cache"}}).
This can be error prone (typo, refactoring ...). The CDI integration module provides the possibility to associate a qualifier to a cache. This qualifier could be re-used to provide a type safe selection of the cache used by a JCache interceptor. Something like:
{code}
public class GreetingService {
@CacheResult @GreetingCache
public String greet(String name) {
return "Hello" + name;
}
}
{code}
Here we need to be in sync with JCache specification. In my understanding of the spec the cache name is required for {{@CacheRemoveEntry}} and {{@CacheRemoveAll}} (but currently in the API there is a default value). For {{@CacheResult}} if no cache name is defined a default one is used.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (ISPN-1491) Provide methods to retrieve the CacheKey parameters
by Kevin Pollet (Created) (JIRA)
Provide methods to retrieve the CacheKey parameters
---------------------------------------------------
Key: ISPN-1491
URL: https://issues.jboss.org/browse/ISPN-1491
Project: Infinispan
Issue Type: Enhancement
Components: CDI integration
Reporter: Kevin Pollet
Assignee: Kevin Pollet
Fix For: 5.1.0.BETA4, 5.1.0.FINAL
Currently, it's not possible to retrieve the parameter values composing the {{CacheKey}} (generated by JCache interceptors). For that, we could introduce two interfaces.
* {{SimpleCacheKey<T>}} used when only one parameter is used as key. This interface could add the following method {{T getValue()}}
* {{ComposedCacheKey}} used when the key is composed by more than one parameter. This interface could add the following method {{Object[] getValues()}}
Here, we need to ensure that we are compliant with the specification.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] Created: (ISPN-1403) Optimise sending Hot Rod topology updates for distributed caches
by Galder Zamarreño (JIRA)
Optimise sending Hot Rod topology updates for distributed caches
----------------------------------------------------------------
Key: ISPN-1403
URL: https://issues.jboss.org/browse/ISPN-1403
Project: Infinispan
Issue Type: Enhancement
Components: Cache Server, Distributed Cache
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 5.2.0.FINAL
Right now, whenever a Hot Rod client sends a request with a view id which is different to the one on the server, it'd get a brand new view in the response to the request. This could be optimised nicely by only sending back a new view id when the server discovers that the client is using an inefficient view. For example, in distributed caches, the moment it gets a request for a key which lands on a node that does not own the key, it could decide to send back the view.
This would reduce the number of times the view is returned, hence improving the performance of requests.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month