> -----Original Message----- > From: Stephen Moretti [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 07, 2003 4:22 AM > To: CF-Talk > Subject: Re: yet another locking ? > > > Jim, > > > > > 3) However, and here's the tricky part, although CFMX won't > crash due > > to poor locking there's also no gaurantee that it'll return proper > > values. The internal locking (implemented in Hash Tables) is, as I > > understand it, much more "atomic" than CF 5.0. > > > > If, for example, you have two nested structures I think > that one could > > be locked while the other isn't. This means that you might > read the > > "good" version of the child while the parent is being written (and, > > presumably before the child is written too). > > > > I'm not certain, but this looks like a race condition to me.
Sort of... But in 5.0 the whole shebang was considered a single unit (sort of). So if the system automatically locks (as it does in MX) does it lock all members of a nested structure set when any of the members are accessed? In other words whether we call it a race condition or not, do we have to lock it? Jim Davis ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 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 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
