You can also have fun with creating a Settings Object to store in the application scope as well instead of just placing the values directly in the application scope...
-----Original Message----- From: Matt Robertson [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 12:53 PM To: CF-Talk Subject: Re: When to use Application var? I would use the cached query / request scope if I had to worry about CF5 compatibility. Then it will keep you from having to worry about cflocking. If you are on CF6+ and know your code will always stay there use the application scope. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com <http://mysecretbase.com> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:218317 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
