On Friday, Oct 4, 2002, at 14:27 US/Pacific, Dave Watts wrote: > This is true for versions prior to CF MX. For those versions, you > should use > the SCOPE attribute. Sean's point is only applicable to CF MX, in > which you > only lock to prevent logical errors - in that case, you want your lock > to be > as "small" as possible in its scope, and using the NAME attribute > allows you > to do that.
Yes, I should have been clearer. My comment was for MX only. The CF product team recommend using named locks in CFMX instead of scoped locks. I no longer have the email to hand that explains all the reasons but, apart from narrowing the zone of the lock, CF has some built in machinery for detecting named lock conflicts that does not apply to scoped locks. An Architect's View -- http://www.corfield.org/blog/ Macromedia DevCon 2002, October 27-30, Orlando, Florida Architecting a New Internet Experience Register today at http://www.macromedia.com/go/devcon2002 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm
