Doug, could you give us an idea of which "obscure methods" changed in the API? We want to know what to look for to watch when we upgrade to this revision. Thanks, Doug S.
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". Just my 2c! Best Wishes, Peter On 10/9/06 10:04 AM, "Tom Chiverton" <[EMAIL PROTECTED]> wrote: > On Monday 09 October 2006 14:49, Beth Bowden wrote: >> Your database should also cache the queries which would help further > > I would be inclined to go this route myself, at least for version 1, and leave > results caching to CF and the database. > As to a UI for doing it in Reactor, I prefer > <object name="Foo" cacheMinutes="10" /> > in the XML out of the options so far, because everyone* already knows that is > where you go to configure Reactor. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
