>to (at beginning of script) copy your session structures to the >request scope, utilize them from the request scope during processing, >and then copy them back to session at the end?
Definitely unnecessary in CFMX. I'd certainly be interested to see where you have been reading that! The only reason to do this pre-MX would be to avoid having to locks all over the place, so might be done if you had a variable you accessed a lot in your application. Generally though if that was the case, it would be best to not use a complex structure that needed duplication. Now, you only have to worry about race conditions for reads and writes in the session scope, which as Dave says, are fairly rare. I'm not sure I've run across any, but then I don't tend to have stuff in Session scope used for computations. One thing to keep in mind is there are times you may want to lock other than just race conditions. However, those generally are more for application and server scope where you may want to lock to prevent multiple threads trying to create them at the same time when under load. --- Mary Jo ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:268193 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
