> > Client variables don't need locking. Why you you need CFLOCK? > > Multiple users could be trying to access the same file on the server via a web inface I created. > <cfdirectory etc...
In this case, you need to CFLOCK the operations that may be shared by different users at the same time. For file operations, used a named lock around CFFILE or CFDIRECTORY. For DB operations, either put a lock around CFQUERY or implement some DB-specific measures. Neither of these should impact your session management method, or vice versa. > > What version of CF are you using? > > v5 Then you do need to CFLOCK session/application vars. Check out: http://www.macromedia.com/v1/handlers/index.cfm?id=20370&method=full Gyrus [EMAIL PROTECTED] work: http://www.tengai.co.uk play: http://www.norlonto.net PGP key available ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com
