> > There are legitimate uses for the Application scope. > > In what situations would you need to use the Application > scope which couldn't be handled by the Request scope? I've > never been able to think of any good examples.
Sure, there are plenty. Basically, they fall into two categories: 1. Variables whose values change over the lifetime of the application. For example, if you want to track how many users are currently in the application, an application variable would be ideal. 2. Variables which are too expensive to populate on each page. Queries stored in the Application scope are a good example of this. It's important to remember that, no matter what you're doing, there are probably alternative ways of doing it, and those alternatives will have their pros and cons, and it's up to you, the programmer, to determine the best way of doing the task in that situation. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
