RE: CFLOCKs.... is this really necessary?

[Al Musella, DPM]

   For things like datasource names, wouldn't it just be easier to define 
it in application.cfm as a local variable? Why add the overhead of 
locking   / checking if it is defined then setting it, etc... at all?

<cfset DSN = 'mydata'>

instead of

<cflock ...>
   <cfif not(isdefined(application.dsn))>
        <cfset application.dsn = 'mydata'>
   </cfif>
</cflock>


I am getting away from all application and session variables on my new 
sites.  They became more trouble than they are worth.

Al Musella
a1webs.com





>They *should* be locked.  Realisticly, I've got a million-hit-a-month
>site that does:
><Cfquery name="blah"
>datasource="#Application.OLEDBDSN#">...</cfquery>

------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit 
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a 
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.