********************** Macromedia Representative **********************
I think the author _implied_ that you should use duplicate() instead of
'cfset', but simply didn't say it. I haven't read the whole article, so I
could be wrong. Anyway, you are correct. If you want to use the Request
scope to store app and session stuff, use Duplicate(), and make sure you
have the Duplicate() hotfix applied.
=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Macromedia
Email : [EMAIL PROTECTED]
ICQ UIN : 3679482
"My ally is the Force, and a powerful ally it is." - Yoda
> -----Original Message-----
> From: Jon Hall [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, April 26, 2001 6:49 PM
> To: CF-Talk
> Subject: More locking confusion...
>
>
> Ok I got the devcenter mailinglist today like a lot of us, and I was
> checking out the article titled ColdFusion Methodologies for Content
> Management at http://www.allaire.com/handlers/index.cfm?ID=20750.
>
> The author writes:
> "An easy answer to this problem is to dump the entire SESSION or
> APPLICATION
> scope into the REQUEST scope. ColdFusion does not 'share' the
> REQUEST scope
> between threads and it does not need to be locked. So by dumping all the
> shared variables to this scope, we can lock our variables once and then
> forget about it."
>
> Well I thought that cfsetting a session or application variable
> to a request
> scoped variable only set a pointer to the original variable so
> these request
> variables need to be locked too. I thought this is what the duplicate() is
> supposed to do (when it's fixed :-)).
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
