Out of the scopes you mentioned you only need to lock "Application" - and
this really only on CF 5.0 or below.

You might do something like:

<CFOutput Query="GetVars">
        <cfif find(VariableName, "Application.")>
                <cflock scope="application" type="Exclusive" Timeout="2">
                <CFParam name="#VariableName#" Default= "#VariableValue#">
                </cflock>
        <cfelse>
                <CFParam name="#VariableName#" Default= "#VariableValue#">
        </cfif>
</cfQuery>

Jim Davis

> -----Original Message-----
> From: Shahzad.Butt [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 8:37 AM
> To: CF-Talk
> Subject: Locking Vars
> 
> 
> Hi,
> 
> I am running a query and setting my application, request and client vars
> in the loop like that
> 
> <CFOutput Query="GetVars">
>     <CFParam name="#VariableName#" Default= "#VariableValue#">
> </cfQuery>
> 
> I am not using session varaibles at all but only CLIENT, REQUEST,
> APPLICATION. Which type of LOCK and which order is recommended in this
> particular scenario - provided that deadlocks are avoided as well......
> 
> Thanks
> Shaz
> 
> 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
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

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to