Hi Jamie,
If you are using CFMX then you no longer need to bother locking when you set session variables.
If you are still in CF4.5 or CF5 then you do need to lock all access to session variables but it depends on the update scenario as to whether you should do them all at once or individually. Generally I have bundled all setting of session vars into one cflock statement. ie:
<cflock scope="session" type="exclusive"> <cfset session.custid = #value#> <cfset session.shipto = #value#> <cfset session.shipid = #value#> </cflock>
hth,
Brett B)
Jamie Lawrence Jenner wrote:
Hi,
I have an app where once logged in three session vars are set for each user.
i have locking on them at the moment as such
<cflock scope="session" type="exclusive"> <cfset session.custid = #value#> </cflock>
<cflock scope="session" type="exclusive"> <cfset session.shipto = #value#> </cflock>
<cflock scope="session" type="exclusive"> <cfset session.shipid = #value#> </cflock>
once set the session.custid wont be changed but the shipto and shipid values can be changed
Is this the best method to use?
cheers
Jamie
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
-- Brett Payne-Rhodes Eaglehawk Computing t: +61 (0)8 9371-0471 f: +61 (0)8 9371-0470 m: +61 (0)414 371 047 e: [EMAIL PROTECTED] w: www.ehc.net.au
--- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
