[jboss-dev-forums] [Design of JBossCache] - JBoss Cache Public API

[manik.surtani@jboss.com]

So I've started on work on JBC 3.0.0.  I don't intend to make any public API changes, the main new features are internal, but significant enough to warrant a major version update.

But, if anyone can convince me of any reasons why the public API does need to change, now would be a good time to do it.

Specifically, genericisation of the Cache interface - which happened in 2.0.0 - is not something I'm overly pleased with as I find it clunky.  What do people think, should it stay or go?

Ah, there is one public API that is due for a change though. Fqn.  No more public constructors, all Fqn construction needs to go through factory methods (which have been in existence for some time now).  This will help us optimise Fqns later as needed.  Also, Fqn generics are going away.  This has been more than just clunky, in fact downright error-prone.  And without much value-add.

Thoughts, comments?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4155390#4155390

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4155390