> So do you recommend locking all updates, even if no session > or application > variable is around? If so, do you use named locks versus scoped?
You should Lock all updates to Application, Session and Server variables, but not other scopes - the only thing about Locking is that if you don't do it, the server has to ensure it's the only application/page doing the update, which adds to it's load Personally I'd lock anyways, it lightens the load for a tiny extra few lines... Worth it in my book Oh, and obviously you don't lock every CFSet if you have a block of them - lock the block... I've seen code (inherited from another company) where they put a CFLock around every single CFSet in a block of 30 in a row... Philip Arnold Technical Director Certified ColdFusion Developer ASP Multimedia Limited Switchboard: +44 (0)20 8680 8099 Fax: +44 (0)20 8686 7911 www.aspmedia.co.uk www.aspevents.net An ISO9001 registered company. ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. ********************************************************************** ______________________________________________________________________ Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm 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
