They don't make it a default behavior because it causes CF to check every instance of every shared variable read/write to make sure it's locked. That causes a lot of performance loss. If you lock them yourself CF doesn't have to look for them to make sure they are locked.
______________________ steve oliver cresco technologies, inc. http://www.crescotech.com -----Original Message----- From: stas [mailto:[EMAIL PROTECTED]] Sent: Monday, January 28, 2002 10:16 PM To: CF-Talk Subject: Automatic CFLOCK read AND write If it is so dangerous to reference shared scoped vars without CFLOCKing them first, then why not that make it default behavior? Frankly, it's just becoming annoying to keep doing this all the time - especially when you inherit an application from somebody else. It's CFLOCK this, CFSETTING that. If somebody wants to override that, maybe there should be a <CFDONOTLOCK> tag. It would be definitely be much less typing! Basically, it's like chipping your car to remove the rev limiter - if you want to do it, go ahead, but at your own risk. ______________________________________________________________________ Why Share? Dedicated Win 2000 Server � PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation � $99/Month � Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusionc FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
