In any case problems at this level could cost you the reliability of theNot true as I stated over and over during the pre-CFMX timeframe. I worked on many high load CF applications that were able to make use of shared memory scopes without using locks including one that was featured as an Allaire case study. It wasn't that I had some magic luck that things worked as the did, the applications were designed specifically such that even without locks there would never be an instance where corruption of shared memory could occur.
server. This is where the "lock everything, all the time" mindset comes
from: if you didn't (in pre-MX) your application would simply not be stable
under load.
You had no choice but to lock - not doing so would result in twitchy server
death.
Remember, that if always locking everything was a rule that was really true, there would be no need for developers to apply locks in the first place since such a simple rule could be handled by the server.
Matt Liotta President & CEO Montara Software, Inc. http://www.MontaraSoftware.com (888) 408-0900 x901
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
