On Monday, Aug 18, 2003, at 07:13 US/Pacific, Alan Ford wrote:
> What it does affect are other threads running
> concurrently, so it's a nonsense to deal with the documentatuion as if
> the
> only thread that exists is this one.
You're still misunderstanding: the documentation specifically
acknowledges multiple threads but my point is that if you have:
<cflock name="somename" type="exclusive">
...
</cflock>
then all requests that run this particular piece of code will be
single-threaded through the cflock tag. And that's exactly what the
documentation says.
> a) two instances of the same thread - cflock works as described
You're mixing your words now. Threads are unique so you can't have two
instances of the "same" thread. You can have two separate, distinct
threads that are both running the same CF page - it's the *code* that
is the same, not the threads.
> A great deal. You (and others) are certainly enhancing my
> understanding of
> the nitty gritty of locking.
OK, good - I'm always happy if we're helping each other learn.
Sean A Corfield -- http://www.corfield.org/blog/
"If you're not annoying somebody, you're not really alive."
-- Margaret Atwood
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/lists.cfm?link=t:4
Subscription: http://www.houseoffusion.com/lists.cfm?link=s:4
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community.
http://www.fusionauthority.com/ads.cfm