Thanks, that is very helpful. On 2/20/06, Michael Dinowitz <[EMAIL PROTECTED]> wrote: > > Probably old code plugged into the onSessionEnd. Application.cfc was one > of > the features we talked about back in 2001 before MX came out. It took a > version or two to get it out but it's here. In MX, there is NEVER a need > to > lock memory variables other than where a race condition exists. As the > onSessionEnd always comes after an onApplicationStart, there should never > be > a race condition unless application variables are being added or modified > outside the onApplicationStart. > > > When accessing the application scope in the onSessionEnd function in > > Application.cfc should you lock in the scope of application or with a > > named > > lock? > > > > The reason I ask is because the documentation uses a named lock and the > > onSessionEnd function cannot reference the application and session > scopes > > directly. > > > > Thanks, > > > > Joe > > > > > > > >
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:232953 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=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
