[infinispan-dev] public API/what should be preserve between minor releases?

Manik Surtani manik at jboss.org
Thu Nov 22 12:06:32 EST 2012


On 21 Nov 2012, at 17:02, Mircea Markus <mmarkus at 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?

- M

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Platform Architect, JBoss Data Grid
http://red.ht/data-grid

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20121122/5a123174/attachment.html 


More information about the infinispan-dev mailing list