There's something that's been buggin me: Is NAME LOCKING sufficient for session variables?
A best practice in CF is to always lock session variable access, but it's not really clear whether 1) NAME locking is sufficient or 2) should we always lock with SCOPE=SESSION? To me, the answer seems to depend on how shared memory is managed in CF. If session scope memory is managed as an entire block, then we have to use SCOPE=SESSION, because different user sessions can corrupt each other. On the other hand, if session scope memory is managed variable by variable, then we only need to worry that a single variable is not simultaneously accessed by two different threads, in which case a NAME lock would be sufficient. Are there any MACROMEDIA folks out there who know enough about CFAS internals to answer this? ===== I-Lin Kuo Macromedia CF5 Advanced Developer Sun Certified Java 2 Programmer ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Get the mailserver that powers this list at http://www.coolfusion.com FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/[email protected]/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
