On 12/14/01 11:24 AM, "Chris Shenton" <[EMAIL PROTECTED]> wrote:
> 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. > Each cache is unaware of what the other one has or is doing. Nope, Aaron's package handles this I believe. He can correct me if I'm wrong. > Seems the caching should be done by the DB machine so the views it > presents are consistent to front-end boxes. I think it can be done in a distributed fashion, but Aaron has a lot more experience in this area than I so maybe he can answer your question with some degree of authority. > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
