> > Jason van Zyl <[EMAIL PROTECTED]> writes: > > > >> I now have Aaron Smut's caching code which I will add to 'stratum' which > >> will be the repository for all the common code used in turbine and code that > >> is currently in velocity that was originally taken from turbine. Over the > >> holidays I will get stratum up on the apache box. The caching package kicks > >> some serious ass. > > > > If multiple front-end Turbine servers implement DB caching in front of > > a single back-end DB server, won't the Turbine machines get out of > > sync? > > Aaron's package can take care of if you wanted to do the caching on the > application machine.
I know I should really wait for the import of the cache package but... Is Aaron's package Torque-specific or a generic cache package? One thing is implementing a LRU cache service, and its quite another to have it work with the existing persistence framework/mechanism. One thing I've done in preparation for the cache is to create an ObjectBroker, through which all my application logic makes database requests. This means that its transparent to the application whether or not a cache is actually used. However, due to the way Torque's business objects are created, after the business objects have been returned to the calling code, a cache is effectively useless since invoking something like book.getAuthor() basically makes a direct database request, bypassing the cache (_unless_ the cache sits between the objects and its peers, which would make it pretty Torque-specific and involve extensive modifications to Torque code, I think). If it is a generic cache package, I would love to see it go into Fulcrum. I'm not entirely satisfied with the GlobalCacheService. Don't know if anyone has bothered, but Expresso has a pretty decent cache. I think the license is compatible with Apache's (hey, they call it an Apache-style license). I've ported it over to Fulcrum's service framework, with some modifications, if anyone's interested. Regards, Kelvin Tan Relevanz Pte Ltd http://www.relevanz.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
