On 2010-07-30, at 12:10 PM, Vladimir Blagojevic wrote:
Sure, sure. I complicated it unnecessarily :)
We might need only one callback on master node. But how do we do design it properly to
accommodate the need of the task to do some task input interpretation using interaction
with cache and return list of preferred execution nodes at the same time?
How about just DistributedCallable#getRelatedKeys(EmbbededCacheManager cm)?
Actually we need to know which particular Cache DistributedCallable(s) will use in
addition to keys.