And don't forget clustered servers where the same application will have its own cache on each server instance (we have this scenario - we are careful about our data usage patterns and what we cache but we also have a web service driven cache updater that can be programmatically triggered to refresh individual cached objects on other servers in the cluster).
As Barney says, this stuff can do your head in... On 10/9/06, Peter Bell <[EMAIL PROTECTED]> wrote:
I may be the only one, but I don't love setting cache times as opposed to using an IsDirty mechanism. If another application may edit your data, it may edit it in a second or in a week. Satisficing on x minnutes as an acceptable latency is OK, but not great. I'd love to see optional object based query caching with an isdirty intercepting inserts, updates and deletes and a big warning message in the docs that said "if other applications touch your database or you have non-reactor db modifications or you use triggers, or you've written your own queries using the query object that modify data, then don't use caching - otherwise enjoy".
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
