Thank you Sean. I was not aware of the intricacies of locking in CFMX vs. CF5. I will have to re-read the docs now.
NAT > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Sean A Corfield > Sent: Monday, July 28, 2003 7:54 PM > To: [EMAIL PROTECTED] > Subject: Re: [CFCDev] CFCs in memory > > > On Monday, Jul > > CF5 needed thorough locking because failure to lock could lead to > memory corruption and other nasty problems. In CFMX, you do > not need to > lock at all if you don't want to - you will not suffer memory > corruption. In CFMX, you only need to lock if you wish to avoid "race > conditions", i.e., to prevent two threads updating the same > variable at > the same time. <snip> ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the word 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
