> It goes on to give an example where they CFSET a local variable to an
> application variable. I don't know whether they are passing by reference
or
> not, but leads me to think that locking aliased local variables that refer
> to Application or Session scoped variables is a good idea.
I am using a thread-safe COM object in an application scope to create
session-specific COM objects (connections to an aardvark database system
[EDA to VAX RDB]). As far as I can tell, I don't need to CFLOCK access to
any of the COM objects involved, because they are designed to be
thread-safe.
It is quite plain that simple variables are not thread-safe in CF. Does
anyone know whether CF structures are thread-safe or not? The MFC have
thread-safe collection classes, but I don't know if Allaire 'rolled their
own' for Cold Fusion.
It seems to me that locking could much better be managed by CF using
thread-safe Variant objects that provide inherent locking and reference
counting than by the current system...
+============================================
+ Benjamin Smedberg
+ CUA Web Developer
+ [EMAIL PROTECTED] - http://computing.cua.edu/as/bds/
+============================================
+ Remember, man, that thou art dust, and
+ unto dust thou shalt return.
+============================================
------------------------------------------------------------------------------
Archives: http://www.eGroups.com/list/cf-talk
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.
