With regard to who is using JCS (or should!).

We use it at http://www.officedepot.com  Without it I doubt we would be
ranked where we are on http://www.ecommercetimes.com/ectpi/

We added a new persisting backend based on an all Java version of gdbm.
I found that in a very old version of w3c's Jigsaw server. We also
enhanced the p2p caching based on the hashing algorithm used by Squid.
Yes we were going to contribute but at the time the JCS folks were
trying to extricate JCS into a standalone CVS code base.  Things were in
flux to say the least.

I have a hard time imagining a substantive website without a JSC
component.  Forward caching of data is just too critical for site speed
and scalability.

Quoting from Jakarta
"The goal of the Apache Jakarta Project is to provide commercial-quality
server solutions, based on the Java Platform, developed in an open and
cooperative fashion".

>From our perspective JCS is on par with Lucene or Log4j, and even Struts
as an invaluable server solution component and deserves equal treatment.

Regards,

Ray Racine


On Fri, 2003-12-05 at 08:08, Brian McCallister wrote:
> OJB supports using JCS for distributed caching, but I don't know how 
> many people actually use it (we don't). There is overlap between OJB 
> and Turbine contributors
> 
> Arrowhead ASP, a GPL ASP interpreter, ( http://www.tripi.com/arrowhead/ 
> ) also uses JCS as I know the guy who wrote it =) OTOH I don't think he 
> has ever submitted a patch or even feedback back to the Turbineers.
> 
> I would prefer to see it split off to its own [sub]project if it has 
> the community around it, but I cannot commit to contributing to it.
> 
> -Brian
> 
> On Dec 4, 2003, at 5:35 PM, Andrew C. Oliver wrote:
> 
> > So far it sounds to me like JCS is only used by Turbine and that only 
> > the
> > Turbiners really care about it.  Thus I don't see why it doesn't just 
> > get
....elided....


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to