Maybe only cache current data? If it's less likely someone will look at last
years entries, exclude them from the cached data. It'll be easiest to wack
it all in there and see how it works out, if you think it might be a problem
then look at ways of trimming the amount you cache.

Ade

-----Original Message-----
From: Bryan F. Hogan [mailto:[EMAIL PROTECTED]
Sent: 23 February 2005 22:17
To: CF-Talk
Subject: RE: Reason to *not* store lots of data in Application scope?


You're right. I was thinking of references to objects not the data.

If Damien is talking about storing the articles in the application scope I
would write them to disk and include them. And then just update them as
needed instead of storing them to memory.

-----Original Message-----
From: Adrian Lynch [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 23, 2005 5:11 PM
To: CF-Talk
Subject: RE: Reason to *not* store lots of data in Application scope?

"I would try and find a way to store references to my data instead of the
data itself."

Surely that defeats the purpose, no? The data is either in a DB/text
file/some remote place, the reference to it would be the least thing you'd
change if you wanted to cache anything.

What do you think?
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 266.4.0 - Release Date: 22/02/2005


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
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:196210
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

Reply via email to