Thanks for the quick reply. So it's a caching implementation. My first thought is that it might have the wrong name. If I were to build a common interface for all caching implementations today, I think I might want to name it commons-caching, since it goes along well with the idea of commons-logging.
Secondly it seems like if this is not actively being developed, it may not ever make it out of the sandbox, especially with the JCS cache impl already existing in the jakarta project. Does jakarta really need two caching implementations? What I am getting at is I think I am interested in starting a project around the idea of a thin wrapper around other caching implementations. I think the name commons-caching would be great for this since it's pretty self-explanatory. I am also interested in starting yet another project called commons-caching-administration which would be a generic caching admin tool wrapped around commons-caching. Any thoughts? -----Original Message----- From: Rodney Waldhoff [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 14, 2004 1:31 PM To: Jakarta Commons Developers List Cc: [EMAIL PROTECTED] Subject: Re: commons cache On Wed, 14 Jul 2004, Baum, Karl wrote: > The project almost seems like yet another caching implementation in > itself, not a thin wrapper (I could be wrong though since I just > quickly looked it over.). No, that's right, it's YACI, although I believe it pre-dates some of those you mention. > I am wondering [...] if it's still > actively being developed? No, it's not, although the existing code is functional. > Karl --------------------------------------------------------------------- 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]
