Here is something to ponder:-) Although it might not be an issue to some of you, but look at it this way. If the website is going to be a high traffic website, then Disk access needs to be considered in the time that a page takes to run.
The more cfincludes that a request needs, will always add to the overhead of the time the application needs to run. If we are talking about a website that is low then forget what I am saying, but if you have a cfinclude that takes say 10ms to run. The multiply this by the number of users that could potentially hit the site, you'll see that this time can bring a servers performance to a critical level. Might not sound like it is a big deal, but can be when the time comes:-) -----Original Message----- From: Bud [mailto:[EMAIL PROTECTED]] Sent: Thursday, 27 June 2002 12:36 PM To: CF-Talk Subject: Re: What is the best variable scope? On 6/26/02, Dave Carabetta penned: >Without belaboring this thread, pre-MX, I don't advocate >using shared-scope varaibles such as the application scope for these sorts >of variables. Period. Exactly. I never did see any reason to store a datasource name, or anything that you have to actually type, as anything but a local variable. If I have to type <cfset application.dsn = "mydsn"> <cfset variables.dsn = application.dsn> and place a lock around it, why not just type <cfset variables.dsn = "mydsn"> ?? -- Bud Schneehagen - Tropical Web Creations _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ ColdFusion Solutions / eCommerce Development [EMAIL PROTECTED] http://www.twcreations.com/ 954.721.3452 ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.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
