If it is a calendar display your wanting to cache go ahead. It'll depend on how many users your getting.
-----Original Message----- From: Damien McKenna [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 23, 2005 5:13 PM To: CF-Talk Subject: RE: Reason to *not* store lots of data in Application scope? > -----Original Message----- > From: Bryan F. Hogan [mailto:[EMAIL PROTECTED] > > It will depend on the amount of memory you have on your machine. That's isn't a problem, there's plenty to spare. > I don't think it is wise though to stuff data other than simple > variables or CFC objects. I was thinking of storing the parsed data, i.e. I'd have a file that would load the data from the database, process it (e.g. collate a calendar) and store it in the Application scope for faster display as the visitor loads the page. > I would try and find a way to store references to my data instead of the > data itself. I couldn't see the reason to do that myself. OK, maybe leaving the e.g. event details in the database while caching the event list, but the whole point is to cache data rather than having to load and process it constantly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:196211 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
