ColdFusion MX and Locking

Does the same hold true with Session vars? My only objection to this article is the statement that recommendations from previous versions have not changed. While the article does describe race conditions and why you need to lock them, it makes it seem like the old rule ("ALWAYS LOCK OR YOU WILL DIE!" ;) is still true. This is simply not the case. If you are using Application vars, for example, as pseudo-constants: <cfif not isDefined("application.foo")>   <cfset application.foo = 1> </cfif> <cfoutput>#application.foo#</cfoutput> There is no reason to lock these lines. ======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email    : jedimaster@mindseye.com Blog     : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > Ah, and the truth be told. Great thanks Massimo! > > > Could someone explain to me the "truth". > > > You may try this: > http://www.macromedia.com/support/coldfusion/ts/documents/tn18235.htm ---------------------------- Massimo Foti Certified Dreamweaver MX Developer Certified Advanced ColdFusion MX Developer http://www.massimocorner.com/ ----------------------------