Ben Forta

By now most ColdFusion developers know that access to shared variables must be locked, but many developers mistakenly think that SESSION variables need no locking if frames are not being used. The truth is, SESSION variables are usually accessed by a single thread at a time, but if users hit refresh, or if network and connection problems cause retries, then there is a very real chance that more than one thread will be active for a single SESSION. So yes, SESSION variable access must be locked (either that, or single thread SESSION variable access in the ColdFusion Administrator). (Applies to: ColdFusion 4 (or later))