I agree. There are some differences in the implementations of each cache. For the most part though, all good caching implementations only expose a get,put, and remove to the application. This is very much like logging which exposes log info/debug/error statements. The real challenge would be finding out what features almost all caching implementations support and coming up with a generic way to access these features. I think we can probably find enough features in common to enable us to build administration tools around commons cache. I actually wrote a large company's caching implementation about a year ago, and most of our time was spent designing an admin tool to allow them to view and modify their caches. I think it would be very powerfull to say that anyone who uses a wrappable caching implementation such as JCS, EHCache, or SwarmCache can use our commons caching adminstration tools. (Just thinking outloud).
-----Original Message----- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 4:22 PM To: Jakarta Commons Developers List Subject: RE: commons cache Hi, >I feel your pain with these classloading issues, however we can leverage >what you've learned in commons-logging in a commons caching project. I >think there is a lot of potential to create something that other >projects can really benefit from using. Sure. It's a bit of a chicken and egg problem though: will they use it if it's immature and vice versa. People who use a caching component as opposed to writing their own hacks are probably pretty serious about the cache working well. Furthermore, the caching implementations seem to have a more differing feature set than the logging implementations. So the next thing to do might be to ask caching impl people (Cameron Purdy comes to mind) what their opinion is (which is of course not binding in any way ;)). Yoav This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- 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]
