> > 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.
I know that this is only a typo, but you meant "Not locking variables ...", right? And in support of Sharon's statement, just yesterday I did some troubleshooting work for a client whose public site was failing under load - and not even that much load, really. The problem? Unlocked memory variables. Whoever built the application in the first place didn't bother to lock them consistently. The result? Approximately one week of downtime, during which this client couldn't do their primary, line-of-business task. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ______________________________________________________________________ This list and all House of Fusion resources hosted by CFHosting.com. The place for dependable ColdFusion Hosting. 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
