Hi Brian, I'm not entirely sure what the status is, as I've just been lurking on the list for long awhile now, but we've successfully used JCS in two projects. One was working directly with the JCS API in a Turbine project and the second is via the very nice integration Hibernate has with JCS for Hibernate-wide caching of objects already loaded from the database.
In both instances it's worked really well and noticeably speeds up the app, though I have to admit we haven't put it through really good stress testing that could potentially reveal small bugs here and there. I'm going to venture that the project is both mature and abandoned. In terms of being mature, it has, from the little I know of the code base as I've only used the API, a stable code base. I'm not quite sure it was abandoned...I think everyone is really interested in seeing a successful caching project at Jakarta, e.g. the Hibernate people chose JCS to integrate with, so I'm not sure why the original developers aren't still around, or that it hasn't gained other new developers. I could be completely wrong, but I seem to remember the original author (or perhaps one of the main contributors) works on a commercial caching system as well as JCS. Ideally, whoever the commercial entity is, they could move to having JCS be their base implementation (or having their product become JCS) and then sell services related to it. But I certainly why they'd want to keep it commercial as well. If any of the main developers would like to chip in as to their thoughts on JCS's production capabilities, I'm sure both Brian and I would appreciate it. Thanks, Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
