That certainly does sound preferable to having two LRU Memory Caches and two Indexed Disk Caches... talk about confusing! The interfaces aren't changed, and aren't publicly exposed, so deprecating the buggy code does little to guide the new user in the right direction towards using JCS successfully.
Just my two cents. -Travis Savo -----Original Message----- From: James Taylor [mailto:[EMAIL PROTECTED] Sent: Saturday, April 03, 2004 6:48 AM To: Turbine JCS Users List Subject: Re: JCS fixes/branch > If there are significant changes, one way to go it to add the changed > auxiliaries as new implementations. Then, the old ones can be > depreciated or eventually removed. For simple bug fixes, this is > clearly not necessary. One of the things I did when re-implementing the JGroups auxiliary was to put it under 'auxiliary-builds' with it's own build script and such. I think this is a good idea in general for any new or significantly changed auxiliaries. One nice thing about this is you can have two auxiliaries with the same class names and just choose which one to put in your classpath at runtime: true drop in replacements. --------------------------------------------------------------------- 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]
