[infinispan-dev] Contributing to Infinispan: API, Commons, Core

[Pete Muir]

On 3 Nov 2011, at 11:11, Manik Surtani wrote:

>> API
>> 
>> The infinispan-api module should only contain the public interfaces which can be used in any context (local, remote, etc). Ideally it should not contain any concrete classes, however this rule can be relaxed for small, self-contained classes which need to be referenced from the API interfaces. When promoting interfaces from infinispan-core to infinispan-api, please bear in mind the type of functionality that is being exposed: if something only makes sense for local mode and not for remote mode (e.g. eviction), then it should remain in infinispan-core.
> 
> Perhaps "Interfaces only.  Concrete classes on a case-by-case basis, treated as exceptions, and only after discussion on this list.".  Actually, *anything* that goes in this module should be only after discussion on this list.  :-)

Agreed, I think this is too limiting right now. At some point we may want to expose the local API as well this way as well...