> Why did Allaire design Cold Fusion so you need to lock the variables
> when you use them? Why doesn't Cold Fusion take care of the threading
> issues and locking?
>
> My reasoning is this:
> 1) Much of the power of CF is it's ability to set session &
> application variables.
> 2) According to all the threads I've read you are suppose to <cflock>
> all access to session and application variables.
> 3) If you are suppose to lock all access to the variables, why not
> then have Cold Fusion do it by default?
>
> Am I, as I suspect I am, missing some crucial point on the concept?
I don't know that I have the answer to this. My suspicion is that, when
Allaire introduced memory variables in CF 3.x, they didn't think to lock
them automatically, and now it would require more of an architectural change
than they're willing to make to have them lock automatically now.
There are some automatic locking options, though, such as the ability to
single-thread sessions in the CF 4.5.1 Administrator. I don't know yet how
well that works, but if it works well, then you wouldn't have to lock
session variables at all.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
