What if another page with different code has multiple statements, even though this page has only the one cfset statement? Hitting this page may cause an inconsistent value in the other (depending on what the code is supposed to do).
Also, single threading the app is not necessary - named locks give finer control than locking the whole session. On 4/15/07, Jaime Metcher <[EMAIL PROTECTED]> wrote: > Andrew, > > OK, I'm officially confused. I remember it being nutted out, and the > conclusion being that you *don't* need to lock when writing to a session > variable. A simple <cfset Session.x = y> can't possibly have a race > condition, right? It *may* be part of a multistatement operation that > creates a race condition, but in itself, no way. -- mxAjax / CFAjax docs and other useful articles: http://www.bifrost.com.au/blog/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 The most significant release in over 10 years. Upgrade & see new features. http://www.adobe.com/products/coldfusion?sdid=RVJR Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:275232 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
