: [infinispan-dev] public API/what should be preserve between minor
releases?
On 22.11.2012 04:11, Navin Surtani wrote:
As you see, IMHO such API changes do not have much effect in normal
situations. I can imagine only problems, when the changed methods are
used within dist exec calls
!
- Original Message -
From: Thomas Fromm t...@tfromm.com
To: infinispan -Dev List infinispan-dev@lists.jboss.org
Sent: Thursday, November 22, 2012 8:23:22 AM
Subject: Re: [infinispan-dev] public API/what should be preserve between
minor releases?
On 22.11.2012 04:11, Navin
On 21 Nov 2012, at 17:02, Mircea Markus mmar...@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(CollectionAddress recipients,
On 22 Nov 2012, at 17:06, Manik Surtani wrote:
On 21 Nov 2012, at 17:02, Mircea Markus mmar...@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.
On 21.11.2012 18:02, Mircea Markus wrote:
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
As you see, IMHO such API changes do not have much effect in normal
situations. I can imagine only problems, when the changed methods are
used within dist exec calls and there are (during update or whatever)
different versions of infinispan inside the cluster.
Does this really happen? I'm
On 22.11.2012 04:11, Navin Surtani wrote:
As you see, IMHO such API changes do not have much effect in normal
situations. I can imagine only problems, when the changed methods are
used within dist exec calls and there are (during update or whatever)
different versions of infinispan inside the
