Maybe I am off my rocker here, but could anyone shed some light on this issue in regards to FarCry?
With regards to Farcry this shouldn't be an issue (at least to my knowledge). This is because the current version of Farcry is designed to run on CFMX 6.1. You are correct that multithreaded (and single-threaded) locking is important. Before CFMX if you didn't lock certain variable scopes you were sure to have issues. However, when ColdFusion was rewritten (from CF5 to CFMX) Macromedia was kind enough to fix this problem.
Most of the articles back in 'the day' that emphasized the importance of using <cflock> were written by people like Ben Forta. He explained in detail the repercussions of what could happen (in detail). Since CFMX came out he hasn't written any articles on the topic because for the most part it has been addressed (except for something he calls "race conditions"). Many people like yourself (and me) have been perplexed why people aren't using CFLock anymore (or very little). So back in April 2004 Ben Forta wrote an explanation on his blog to help ease people's worries (link below).
Here is an excerpt:
"ColdFusion MX does not suffer from the memory corruption that plagued prior versions, and so not locking will not harm ColdFusion at all. If the only reason that you ever locked shared memory was to prevent memory corruption, then no, there is no need to lock."
Here is the full blog article link (on his website): http://www.forta.com/blog/index.cfm?mode=e&entry=1139
Hope this helps,
Jeff C.
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
