Add to that list, Server, again though, that rule goes away in MX. (However they are still times when you need to lock.)
======================================================================== === Raymond Camden, ColdFusion Jedi Master for Mindseye, Inc (www.mindseye.com) Member of Team Macromedia (http://www.macromedia.com/go/teammacromedia) Email : [EMAIL PROTECTED] Blog : www.camdenfamily.com/morpheus/blog Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda > -----Original Message----- > From: Critz [mailto:[EMAIL PROTECTED] > Sent: Friday, August 15, 2003 6:57 PM > To: CF-Talk > Subject: Re: I debated whether or not this question was too > stupid to ask... > > > oi Jeff!! > > /nick Raymond Camden > > thou shouldst lock anytime thou writest the word session or > application > > /nick Critz > > is not required in cfmx IIRC > > > -- > > > ------------------------------------ > Friday, August 15, 2003, 4:05:04 PM, you wrote: > > J> Do you lock the *creation* of session variables? > > J> For instance, is > J> <cflock type="exclusive" timeout="30"> > J> <cfset SESSION.MyStruct = StructNew()> > J> </cflock> > > J> Do-able? Bad? Good? Stupid? A Sign of Weakness that the > rest of the > J> pack will surely exploit? > > J> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/lists.cfm?link=t:4 Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 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
