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 :-)).
Am I incorrect?
jon
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
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
