You're talking about developers who don't use CFLOCK because they are ignorant of CF locking issues. I'm sure we all agree that this is a bad thing, but it's not exactly relevent to the original discussion.
You can write perfectly "solid" applications that do not lock session variable access. Simply enable the Single Threaded Sessions option in the CF Administrator. That's been my point from the beginning. It's not helpful to compare this with "sloppy" or incompetent coding. [EMAIL PROTECTED] (formerly posting from junkmail) ----- Original Message ----- From: "Sharon Diorio" <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, March 19, 2002 9:45 AM Subject: Re: UDF question > > The server, admittedly, does not host any > > extremely-high activity sites. > > There's the kicker. Locking variables is something you can *usually* get away with on low traffic sites. But put any load on these sites and you start getting odd errors that are seemingly sporadic (if you're not familiar with locking issues.) Since none of us truly knows what kind of load a site might ultimately have to support, getting into the habit of writing solid code from the start is a good idea. > > Sharon DiOrio > ______________________________________________________________________ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.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
