>Over on our side, I understand Aaron's in the process of importing JCS >(http://jcs.sourceforge.net) into Turbine (stratum, I think?).
I'm just waiting for sufficient karma. >Now I recently discovered that Jakarta actually has not one but _TWO_ >existing caching subsystems, one at Commons and another at Cocoon (which >according to http://marc.theaimsgroup.com/?l=jakarta-commons->dev&m=101045218126806&w =2, are somewhat different and are complementary). >With the addition of Aaron's JCS, Jakarta will likely have 3 caching >subsystems. That's a lot of cache. I was in on the commons discussion some time back. . . . I need to some up with some decent examples and clean up a few things with the explicit grouping, but I think the JCS will be a valuable addition to Jakarta. If it doesn't pan out then of course it will be replaced by a superior product. JCS is pluggable and could perhaps incorporate some of the work from other caching systems. The strategy pattern lends itself to benefiting from community contributions. And since it is close to the JSR 107 specification, the API might become widely familiar and well documented. . . . In the coming moths I hope to devote a good deal of time working with everyone to making it the best caching solution available. I don't care where it goes. I just want it to be useful, easy to use, and the best tool available. I'd like to get started in the stratum repository and see what happens. Aaron -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
