I'm pretty sure I know the answer to this one, but is it necessary to lock application variables reads? or application variables used in an isdefined statement? I'm almost 100% sure you do not need to lock the isdefined, but that the read may need a readonly lock. Can some one confirm this for me?
Brook At 04:03 PM 28/10/02 -0800, you wrote: >Sorry, too late in the day for me. Just session and app vars. > > > > >On 10/28/02 3:52 PM, "Brook Davies" <[EMAIL PROTECTED]> wrote: > > > Client variables locked?? I don't think you have to lock client variables > > do you??? > > We do not use any session vars and only a handful of application variables > > which are all locked. No problems on early versions of CF. > > > > > > > > > > > > > > At 03:41 PM 28/10/02 -0800, you wrote: > >> I know this may be obvious, but are all session, client and app variables > >> locked? Not 100% sure of the role of locking in CFMX but we've seen > similar > >> behavior on CF 5 if an app, high or low-traffic, contains unlocked vars. > >> > >> Ian > >> > >> > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
