Locking in CF7 is now only necessary if you could encounter a race condition, so that you always get the correct value in/from the variable. The memory corruption seen without locking in CF5 and below is a thing of the past.
Therefore SESSION locking is probably unnecessary unless you are using a frameset where multiple pages may access the same session variable concurrently. A user's session is separate from other users' sessions; only the same user requesting multiple pages at the same time can cause a SESSION variable race condition. Multiple browser windows for the same app, a really fast mouse hand and bad luck could potentially lead to the same result. On 9/2/06, Denny Valliant <[EMAIL PROTECTED]> wrote: > > how come not locking <cfparam name="session.someVar" value="whatevervalue"> > is acceptable? -- CFAJAX docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:251843 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
