[infinispan-issues] [JBoss JIRA] (ISPN-2192) Allow using Distributed Execution against any cache (not just clustered caches)

[ https://issues.jboss.org/browse/ISPN-2192?page=com.atlassian.jira.plugin.... ] Randall Hauch edited comment on ISPN-2192 at 8/21/12 9:04 AM: -------------------------------------------------------------- Yes, I originally suggested keeping/using the {{Distributed*}} interfaces because they actually work semantically for all modes - the only thing "distributed" about each of them is simply the name. The "submitEverywhere(...)" is generic enough that I think that'd make sense even in a local cache. However, it may make more sense in the long run to define new interfaces that are named independently of the mode. For example: {code:java} Cache<K, V> cache = ... CacheCallable<K,V,R> callable = ... CacheExecutorService executor = cache.getExecutor(); List<Future<R>> futures = executor.submitEverywhere(callable); {code} Notice how Infinispan should IMO provide a way to obtain a proper {{CacheExecutorService}} implementation based upon the configuration. The example above obtains it from the cache (which IMO would be ideal), though I can see a factory or utility class being useful here. Of course, I could still use my own {{CacheExecutorService}} if I knew which one would work best. Really, this is not very different than using {{DistributedCallable}} and {{DistributedExecutorService}} - just the names have changed slightly. Whether this is important is up to the Infinispan team. BTW, I think that the contract should be that the calling code always has to be prepared to handle multiple Future<R> instances and be able to combine multiple {{R}} results. Even though a naive local executor might only return one, an advanced local executor implementation could parallelize the work and return multiple. was (Author: rhauch): Well, ideally I could execute code like this on any cache: {code:java} Cache<K, V> cache = ... CacheCallable<K,V,R> callable = ... CacheExecutorService executor = cache.getExecutor(); // or perhaps from a utility or factory, // but something that Infinispan provides List<Future<R>> futures = executor.submitEverywhere(callable); {code} Of course, I could still use my own {{CacheExecutorService}} if I knew which one would work best. I'm not sure this is terribly different than using {{DistributedCallable}} and {{DistributedExecutorService}}, since those interfaces actually don't have anything specific to being "distributed" other than their names (which is why I originally suggested simply reusing them as-is). Perhaps if {{Cache*}} interfaces will be created, the {{Distributed*}} interfaces could extend the newer {{Cache*}} interfaces. WDYT? -- 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