Sounds like the basic problem is lack of community.
Getting community involves publicity and time. Publicity involves web
presence and a release.
Unless the rest of the turbine community are highly interested in JCS, I'd
suggest that joining Commons is the best way for you to gain community.
I agree to Henri JCS could need more publicity! I have implemented a
transactional cache for the Jakarta Slide project as the only Apache
caching thing I have found at that time was
http://db.apache.org/ojb/objectcache.html
which simply was not powerful enough.
Even tought ojb caching took
Oliver Zeigermann wrote:
Now information
http://jakarta.apache.org/turbine/jcs/index.html
tells me too little. Can someone explain: does it support any type of
transactions or could it easily be augmented to?
Hope this is not too much OT and thanks in advance,
I think JCS is getting extra
On 1 Dec 2003, at 09:57, Oliver Zeigermann wrote:
I agree to Henri JCS could need more publicity!
luckily enough it's apache newsletter time!
i know from personal experience that writing up something for the
newsletter really does generate interest. JCS sounds like something
that people would
I'm sure JCS would be much more widely used if we got out a release.
Right now, the major impediment is that users have to build it
themselves. If we had a release, more sample applications and further
For a long time I hoped a release could be avoided until after the
JCache JSR was at least in
