> locking on a per-object basis. I'll give you an example. Let's say you're
> retrieving two variables from shared memory:
>
> <CFSET localvar1 = Session.var1>
> <CFSET localvar2 = Session.var2>
>
> If the variables themselves handled their own locking (if, for instance,
you
> instruct the CF server to lock reads automatically in the CF
Administrator),
> you'd end up with the equivalent of this:
>
> <CFLOCK SCOPE="SESSION" ...>
> <CFSET localvar1 = Session.var1>
> </CFLOCK>
> <CFLOCK SCOPE="SESSION" ...>
> <CFSET localvar2 = Session.var2>
> </CFLOCK>
>
> Now, that can be done more efficiently by handling the locking yourself,
> with one set of CFLOCK tags.
Builtin variable locking at the object level doesn't lock the entire
SCOPE="SESSION", it only locks the paricular variable that you are accessing
(as in ASP). This is one of the major pains of CFLOCK, that I must lock the
entire application scope just to retrieve an object reference from what
should be a thread-safe object.
--
+============================================
+ 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.
