Adam, I hear what you're saying (i.e. if a race condition is possible lock it whether it matters or not as a matter of course) and I don't think you're trying to give me a hard time. Just a thoughtful discussion.
With the statements at corfield.org that these guidelines are posted by the Macromedia Web Technology Group, and on the site itself regarding their ownership of same (see the intro) it sure does look as if there's more to this than one guy's opinion. If thats not the case then its bad news to have stuff like that there, if in fact its bad advice. Most of the time my own session and app-scope data is in the form of constants. DSN assignments, user data popped in once after a login, or once upon logout. As such I'm sticking with the no-locking when I am working on an MX+ server for this sort of data. However I'd be very interested to hear a once-and-for-all out of someone at the top of the food chain. Criminy, we see one of these stupid locking threads about once a week. It seems time that if something definitive was put out we could answer the next one with a url and be done with it. -- --mattRobertson-- Janitor, MSB Web Systems mysecretbase.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:206143 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
