You need to lock to prevent race conditions. If that is why you were locking then yes, you should.
But you do not need to lock to prevent memory corruption. So, if that was the only reason you were locking, then no need. -----Original Message----- From: Raymond Camden [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 01, 2002 5:02 PM To: CF-Talk Subject: RE: CF Wishlist > > > From: "Raymond Camden" <[EMAIL PROTECTED]> > > > > cflock is _not_ necessary for memory issues anymore. You > still need it > > for logical reasons. For example: > > > > application.x = application.x + 1 > > Whoah - not been following this thread closely, but did I miss > something? You don't need to habitually lock Session, Server and > Application variables anymore in CFMX? > Correct. But, it doesn't hurt either. I'll probably continue using it just to be safe. ======================================================================= Raymond Camden, Principal Spectra Compliance Engineer for Macromedia Email : [EMAIL PROTECTED] Yahoo IM : morpheus "My ally is the Force, and a powerful ally it is." - Yoda ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
