An application scoped lock works just for that application. A session scoped lock works just for that user's session.
It's all a matter of how an app is structured. Take 10 threads that need to write to different data in the application scope for an app; named locks let them all operate at once, while a scoped lock single-threads the app. On 1/10/06, Robert Everland III <[EMAIL PROTECTED]> wrote: > I would think that named locks would end up being difficult to manage. You > would have to remember that you locked session.variablename with the lock > lockname. My question would be is does locking lock the scope for the whole > box, or only for that application and that scope. -- CFAJAX docs and other useful articles: http://jr-holmes.coldfusionjournal.com/ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:229014 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
