I'd be a little concerned about how you're caching your database in theI would suggest using a most requested/most recent caching approach for objects since it seems to be the best strategy for most apps. It makes sure that the heavily used objects are in memory and the recently created ones, which may not have yet had time to be heavily used.
application scope, however. That's just asking for trouble, IMHO. At the
very least, you should use a revolving cache, so it caches the X most
recently used objects, rather than all of them. You probably want to look
at the build in query caching, and/or DB-level caching, as they'll probably
be a lot better suited for a loaded app. Of course, I've got no familiarity
with your app, so you have to make the call.
I'd also add that storing a lot of XML in a relational database leads to a good number of problems in the long run. If you have a lot of XML, use a native XML database.
Matt Liotta President & CEO Montara Software, Inc. http://www.MontaraSoftware.com (888) 408-0900 x901
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
