You need to use the name attribute to specify a name unique to that locking code. For example, for Session var locking I usually used <cflock name="#CFID#_#CFTOKEN#" ...> The trick is to be consistent with your lock naming so that different code block which you want to lock will have the same name. For Application vars you need a different name since you want application wide locking and not session wide locking. Something like name="Application_Scope" might work. Again, the trick is to be consitant.
</rob> -----Original Message----- From: Gyrus [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 15, 2002 9:55 AM To: CF-Talk Subject: CF4.0 shared scope locking? Another CF4.0-only question... Jeez, I feel like I'm back in the stone age doing this with MX flying around! What's the deal with locking shared scope variabled in CF4.0, which doesn't support the SCOPE attribute for CFLOCK? Instead of: <cflock scope="APPLICATION" type="READONLY" timeout="10"> temp = application.variable; </cflock> Should I use: <cflock type="READONLY" timeout="10"> temp = application.variable; </cflock> ???? Does this do the same job? I suspect not, as the SCOPE attribute wouldn't be necessary if this was the case... If anyone's got any knowledge of what to do here, please let me know! TIA, - Gyrus ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - [EMAIL PROTECTED] work: http://www.tengai.co.uk play: http://www.norlonto.net - PGP key available ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ______________________________________________________________________ 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
