how to properly lock session variables when locking by name 1

[leadman]

I can only use named locking to lock session variables on my site. I have applications that run in subfolders (each subfolder has its own application.cfm template) and each application uses session variables that are unrelated to other applications. My questions are these:

1. If I were using scope level locking (at the session level) would the session variables only be locked within the particular subfolder (application)? or would all session variables on my site be locked.

2. Am I safe using a different lock name to lock the session variable for each subfolder/application (ie., folderonelock, foldertwolock, etc..)

 

[sshhz]

Actually, when you define a unique application name in the application.cfm, it won't conflict with other applications. Since you this application.cfm in every subfolders, it is very safe to use same session name variables among these subfolders and main folders, with the condition that "application name that you define for each subfolders (application.cfm) must be unique".