Yes, they MUST be locked. These look like variables that don't change - I'd do a CFIF test on one, and if it doesn't exist then set them all. As long as you always set them all together, you can use the existence of one to test for all.
This way the app vars are set only once, and don't bog down your pages, since Application.cfm is called with every request. Chris Norloff ---------- Original Message ---------------------------------- from: "Earl, George" <[EMAIL PROTECTED]> Reply-To: [EMAIL PROTECTED] date: Tue, 26 Mar 2002 11:21:07 -0500 >Here is my application.cfm file: > ><cfapplication name="appname" applicationtimeout=#CreateTimeSpan(2, 0, 0, >0)#> > ><cfparam name="application.appnameroot" default="/appname"> ><cfparam name="application.includesDir" default="/appname/includes"> ><cfparam name="application.imagesDir" default="/appname/images"> ><cfparam name="application.menusDir" default="/appname/menus"> ><cfparam name="application.templatesDir" default="/appname/templates"> ><cfparam name="application.smapDir" default="/appname/smap"> > >Should I be locking these cfparam tags? Should I wrap them all in one lock >or should I lock each one individually? > >What is the difference between using cfparam tags as I have above and using >cfif with isDefined and cfset to accomplish the same thing? Is one method a >better practice than the other? > >Thanks! > >George >[EMAIL PROTECTED] > ______________________________________________________________________ Get the mailserver that powers this list at http://www.coolfusion.com 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
