OK, here's one example - We have a system where a huge amount of config data needs to be retrieved from a database for each page. Just retrieving all the DB records takes about 2.5 seconds. If you were doing that every page, then you'll very quickly kill just about any server.
So what we do is convert those DB records to structres, and store them in the Application scope. On each request, we check if the App structure exists, and if it doesn't (or if a particular parameter is passed in the url) call the code that initialises the structure. Then we duplicate the Application structure into the REQUEST scope, which only takes about 50 ms. how's that? -----Original Message----- From: Aidan Whitehall [mailto:[EMAIL PROTECTED]] Sent: 09 November 2001 11:31 To: CF-Talk Subject: RE: Session variables > 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. -- Aidan Whitehall <[EMAIL PROTECTED]> Macromedia ColdFusion Developer Fairbanks Environmental +44 (0)1695 51775 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 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
