I can testify that we have jcs working /w out error at many customer sites running production web farms.
The code is solid. -----Original Message----- From: Eric Everman [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 03, 2007 1:21 AM To: JCS Users List Subject: Re: New Release w/o util.concurrent library? Its just unsupported code at this point and it seems to come from someone's personal webpage. This isn't really the type of thing I want to put in a production project, is it? I trust that the author's intentions are good, but the source seems a bit sketchy, especially for something that provides threading support, which is inherently complex. I'd feel more confident if it were an actively developed project from a known source, or preferably, if the dependency were removed all-together because it seems like the need for it is based on JDK 1.3. --ee On Apr 2, 2007, at 11:51 PM, Smuts, Aaron wrote: > I don't understand your concerns. It's old, but so what. After the > next release, we will move to a jdk 1.4 compliant JCS. Right now > it is > still compiled under 1.3. At that time we can use the backport. > >> -----Original Message----- >> From: Eric Everman [mailto:[EMAIL PROTECTED] >> Sent: Tuesday, April 03, 2007 12:07 AM >> To: JCS Users List >> Subject: New Release w/o util.concurrent library? >> >> Hi - >> >> I'm starting a new project and was wondering if a new release of JCS >> w/o the util.concurrent library is immanent. This library is rather >> old at this point and is in maintenance mode. I'm concerned that in >> current and near future JVMs in complex classloader environments >> (like a J2EE environment), things might start to go wrong. The new >> Java spec includes new Threading capabilities - any chance there will >> be a switch soon? >> >> Otherwise, I think I need to consider some other caching >> implementation, despite the fact that I have used JCS for my past >> projects. >> >> Thanks for a great cache implementation - I hope it stays current, >> >> --ee >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
