Isn't this only true is you have not copied the value back again...? So.
1. Copy Session to Request Scope 2. Set var in Request Scope 3. Copy Request to Session Scope So, in this instance it's not creating a pointer. -----Original Message----- From: Alex Skinner [mailto:[EMAIL PROTECTED] Sent: 05 November 2003 12:24 To: [EMAIL PROTECTED] Subject: RE: [ cf-dev ] Request scope Although copying stuff from shared scope variables into the request scope and back again was pretty common practice to try and minimise the amount of locking required on older apps, be aware that when you do the following. <cfset request.alex=session.alex> that it doesnt actually create a copy rather an in memory pointer to the original, so as such with older cf4.5 and 5 applications when there where problems with accessing shared scopes you could still experience problems with this technique. If you are going to copy stuff from the session scope and especially if youre looping through the whole collection as some code posted was then if they're structures make sure you use the duplicate function, as the structcopy function also does a shallow copy rather than a deep one. Worth mentioning i thought ;-) Alex -- ** 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] -- ** 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]
