> Obviously this caching layer would need some considerable though to
> consider all the access points to modifying the underlying DB to prevent
> the DB and cache becoming out of step. And obviously it would only work
> where the one webapp was the only app accessing the DB. However it would
> allow the om/peer level to maintain consistency in the examples you give
> if implemented properly.
>
> What do you think?
>
I think this would be great, but I have quite a bit of reservation about
implementing something like this in Turbine. The "only one webapp
accessing the db" requirement would be a big scalability problem, where
the purpose of providing the consistent OO model would be to open up the
possibitlities for more complex software. I guess I can see some value,
since the system would be lighter weight than an app server/ejb
environment and so could potentially allow it to be used in smaller
applications, but I am not sure the benefit is worth the cost.
John McNally
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
