Adam, So you're saying that the copying of session scope to request scope and back again is no longer necessary in CFMX? Or at least, the locking of these processes is no longer required? Does this mean I can happily (and safely) use, add or modify any session vars on a template without locking?
Steve -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Adam Cameron Sent: Wednesday, 2 June 2004 8:51 AM To: CFAussie Mailing List Subject: [cfaussie] RE: Form scope weirdness or ........ >this is a CF5 best practice that i have maintained in CFMX. But the reason that existed in CF5 to do this is no longer present in CFMX. There's no need to lock shared-scoped variables in CFMX for the "memory corruption" problem that CF5 has, and this practice in no way protects against race conditions (in fact it makes it *worse* in some cases) which is the other reason to lock shared-scope variables. So tread with caution there, I'd say..? Adam Cameron Senior Application Developer Straker Interactive Ph: +64 9 3605034 Fx: +64 9 3605870 Email: [EMAIL PROTECTED] --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004 --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
