What Peter said - you take a big hit if every read has to check the master cache. You're better notifying other servers if the cache is tainted (and leaving it up to users whether they even want to cache data).
On 10/9/06, Peter Bell <[EMAIL PROTECTED]> wrote:
I'm sure it's obvious, but I just want to mention that the central authority web service would have to have both read and write methods so any server could tell it when an insert or update had been performed. I am also thinking that a publisher: subscriber model might be more performant as you'd get notified whenever a cache was tainted (usually fairly seldom) rather than having to ask if the cache was valid every time you read from the cache (more frequent). Obviously with a model like this the benefits of caching would become more marginal for fast changing data, so I'd make it object specific so you didn't have to cache comments or messages in chat windows.
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
