On 22 Nov 2012, at 17:06, Manik Surtani wrote:
On 21 Nov 2012, at 17:02, Mircea Markus <mmarkus(a)redhat.com> wrote:
> Hi,
>
> Cache, CacheManager and all the API that's in the org.infinispan package needs to
be backward compatible.
>
> What about more obscure stuff, e.g.
> RpcManager.invokeRemotelyInFuture(Collection<Address> recipients,
ReplicableCommand rpc, boolean usePriorityQueue, NotifyingNotifiableFuture<Object>
future);
>
> This is still accessible through cache.getAdvancedCache().getRpcManager(), so it
still counts as public API. I doubt that any user is using that method directly, but OTOH
it's public so who knows.
> What do people think? Shall we be strict with regard to such 'obscure'
methods between minor releases?
More than something exposed via AdvancedCache, it's more of a concern when it comes
to people writing custom interceptors and may have direct access to the RpcManager.
What do you intend to change in the RpcManager?
remove the future argument from all
the methods once my async refactoring is in place.
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)