I don't lock all instances of session var reads or writes and I get like five to ten emails a day from cftries telling me the variable doesn't exist. The error doesn't crash the page, but I'm still getting the emails. I've considered moving all my session vars to a request scope at the top of the page and back at the bottom. Any advice? Why are these session vars being reported as not existing in the first place?
Mik At 03:33 PM 2/28/2007, you wrote: >From > >http://www.adobe.com/devnet/coldfusion/articles/updating_legacy_03.html > >"With ColdFusion MX, there is only one reason to lock application, >session, or server variables, and that is the danger of a race >condition." > >I would add to that statement that the race condition should be >meaningful. If you have a page counter, and it might display one or >two numbers off, and you don't care, then thats also something that >need not be locked. A silly example but it illustrates the point. > >Generally I still lock writes with a scope lock. Dunno why. Paranoid I guess. > >-- >[EMAIL PROTECTED] >Janitor, The Robertson Team >mysecretbase.com > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion MX7 by Adobe® Dyncamically transform webcontent into Adobe PDF with new ColdFusion MX7. Free Trial. http://www.adobe.com/products/coldfusion Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:271002 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
