On 8/1/00, Dave Watts penned:
>The problem with this answer is that you're referencing memory variables in
>your NAMEs without locking those references! This problem has been discussed
>here previously; I'm aware that Allaire's own recommendation under CF 4.0.x
>was to name CFLOCKs using Session.SessionID and Application.ApplicationName.
>Other alternatives have been suggested, but the implicit naming problem is,
>I think, why Allaire added the SCOPE attribute in 4.5.x.
Question. If you are using the cflock to lock access to single
threaded custom tags, etc., what Scope would you use?
--
Bud Schneehagen - Tropical Web Creations
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
ColdFusion Solutions / eCommerce Development
[EMAIL PROTECTED]
http://www.twcreations.com/
954.721.3452
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
