> I have come across some similar code also, moving variables scope into > sessions and back again for no reason.
There's actually a reason why that might be, in some cases. Not a good reason, but a reason nonetheless. It used to be the case (CF 5 and earlier) that you had to worry about locking a lot more than you do now. So, people would do something like this: <!-- top of page --> <cflock scope="session" ...> <cfset variables.localsession = session> </cflock> ... do a bunch of stuff with those variables ... <!-- bottom of page --> <cflock scope="session" ...> <cfset session = variables.localsession> </cflock> Unfortunately, it didn't work very well in practice. > perhaps you could just ask him why he is doing it. I am not being sarcastic when I say this - this is a very good suggestion. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:349693 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
