I started with CF before MX came out and had to deal with locking shared scopes. Nowadays, with MX, unless there is a race condition - you don't have too. In most of my applications, the application scope is subject to race conditions - however, I'm still weary just to reference the application scope directly. Pre-MX days, I had used to copy the application and the session scope into the request.App and request.Ses respectively with duplicate() in the application.cfm and then duplicate back the request.Ses. in the onrequestend.cfm to the session scope etc. I still do this to this day. Then you could just reference request.Ses.XXXX without locking - that saved a bunch of time. What are people's thoughts about locking nowadays - I'm working on an app with the concept of duplicating the scopes to the request - however, a fellow friend of mine is telling me I'm slowing things down. I'm saying "We should lock - just in case - you never know". Thanks in advance.
Peter J. Farrell
Maestro Publishing
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
