Manik,
I am not sure what is "more correct" though? To me, I can see right away that
PojoCache is a feature, but have a hard time to tell the difference between it and Cache
without explaining it in details. I don't know what others think but it doesn't
convey the right functionality that is a HasMap-like "reference" cache.
Of course, detailed explanation will work but key is to first time user, will this create
confusion or not?
-Ben
-----Original Message-----
From: Manik Surtani [mailto:manik@jboss.org]
Sent: Friday, August 11, 2006 9:00 PM
To: Ben Wang
Cc: jbosscache-dev(a)lists.jboss.org
Subject: Re: [jbosscache-dev] Naming discussion
On 11 Aug 2006, at 12:17, Ben Wang wrote:
Guys (and Manik, secifically),
I have been in the process of updating the PojoCache documentation for
2.0 release. One thing that came up that I'd like to solicit some
inputs. As we all agreed that PojoCache will still be housed under
JBoss Cache (alhtough may have two separate distributions).
That is, JBoss Cache will have two cache libararies per se. Now we
know one component is PojoCache. How do we call the other component
(with Cache implementation)? We used to call it TreeCache that is more
distinguished than simply Cache, IMO.
I agree that Cache vs. PojoCache is less distinct than TreeCache vs.
PojoCache, but at the end of the day we're trying to define a product that does a
single task of caching data. As you said, PojoCache builds on top of this to add Pojo/AOP
based features, so one may argue that Cache vs. PojoCache, while being less distinct, is
in fact more correct.
FYI, in 2.0, PojoCache will use a delegate to the Cache
implementation. Actually, there will be two seprate configuration xml
files. One is for the Cache and the other for PojoCache. So we can say
PojoCache is a layer on top but not a sub-class anymore.
Thanks,
-Ben
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev