Guys, its the pointer situation again!

I need you CF eyes....  a third party of mine has developed the following
code to copy session variables into the request scope.  I believe that what
he is performing to be the copying of pointers and not actually 'copying'
the values to the request scope.  Can you take a squizz and see what you
think?  He is using CF4.5 so he has no StructAppend() or correct Duplicate()
function.

<cfcase value="session2request">
<cflock scope="SESSION" type="READONLY" timeout="15">
        <cfloop collection="#session#" item="key">
                <cfset request[key] = session[key]>
        </cfloop>
</cflock>
</cfcase>

he is then referencing the code within a page as request.VARIABLE.   I am
sure that these need to be locked since they are only pointers... what do
you think?

has anyone got a real world example of how to prove what I think is
happening? (since I know a lof you agree that it is a case of pointers!)


Many thanks

Neil


 

-- 
** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For human help, e-mail: [EMAIL PROTECTED]

Reply via email to