[infinispan-dev] Infinispan public API

[Manik Surtani]

Mircea and I were chatting about the HotRod client that he is writing, and we agreed that the best approach as far as API is concerned is for RemoteCache to extend Cache, RemoteCacheManager to extend CacheManager, etc., to maintain familiarity with p2p-style interaction with Infinispan as well as some ease in switching between interaction styles.

One impact of this is that the HotRod client would then have a dependency on infinispan-core.  So the question is, is this OK?  Pulling in a large number of classes that won't really be used except for the super-interfaces?  

One alternative is to pull the public API interfaces out of infinispan-core into a very light infinispan-api module.  This way the HotRod client can just add a dependency on this jar, but it would mean infinispan-core has a dependency on this jar as well.  One side-effect benefit here is that public API will be very clearly defined.

Thoughts?
--
Manik Surtani
manik at jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org