Wouldn't you actually need to use the Duplicate() function here when
referencing the session variable? I seem to recall past discussions that the
process of making a copy in this way actually only created a pointer to the
session variable and left you vulnerable to the locking issue. Using
Duplicate(), however, made a true clone of the variable that was free from
the locking issues. As in.....
<cfset request.session.strFirstName = Duplicate(session.strFirstName)>
#############
<!--- lock session and read name/email address --->
<cflock scope="session" type="readonly" timeout="30">
<cfset request.session.strFirstName = session.strFirstName>
<cfset request.session.strLastName = session.strLastName>
<cfset request.session.strEmail = session.strEmail>
</cflock>
#############
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
