I didn't see earlier posts to this thread, but it is worth noting that if you are using Application.cfc and calling onApplicationStart() or onSessionStart() explicitly, you will still need to lock the appropriate scope(s).
Nic -- Nicholas M. Tunney Blog: http://www.nictunney.com Adobe Certified Advanced ColdFusion MX7 Developer Adobe Certified Instructor Adobe Community Expert Rick Faircloth wrote: > Casey, Matt, & Jim... > > Thanks for the info! > > Rick > > >> -----Original Message----- >> From: Jim Davis [mailto:[EMAIL PROTECTED] >> Sent: Sunday, December 09, 2007 2:14 PM >> To: CF-Talk >> Subject: RE: No Longer Need to Lock Session Variables? >> >> In short you no longer need to do this to ensure server reliability (the >> structures which hold this information are now thread-safe) - no more >> crashes because of locking. (5 year-old Yay!) >> >> (Just kidding - we went straight from 4.5 to 7 so I know exactly where >> you're coming from.) >> >> However you still may need to lock to protect your data for >> application/design reasons (race-conditions for example). It's rare that >> you'll need to lock whole scopes however and for the most part named locks >> should provide all the utility you need without dragging performance. >> >> Jim Davis >> > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Get involved in the latest ColdFusion discussions, product development sharing, and articles on the Adobe Labs wiki. http://labs/adobe.com/wiki/index.php/ColdFusion_8 Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:294435 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
