> Yes it does only set a pointer, I've tested that before and found it to be
> the case.
> However (and I haven't tested this) the request scope by its very
definition
> in CF
> is supposed to be thread safe. Wouldn't this in effect be treated by the
> CFAS as read locked
> pointer?
I *think* you are incorrect here, although I'm not sure. Here's the way I
see it:
The request scope is thread safe in the sense that no two processes for the
same user request will process at the same time. In other words, when I hit
a CF page that single request can not generate simultaneous access to the
request scope. So, any requests I make while on this page will not
simultaneously access the application scope at the same time as another of
MY requests.
However, consider this:
if I have in my request scope a pointer to an application scoped variable,
any accesses of that request scoped variable will in effect access the
application scope. If another user had triggered an exclusive lock of the
application scope, nothing will stop my request-scoped variable from
accessing the locked data at the same time.
Hope that makes sense,
Seth Petry-Johnson
Argo Enterprise and Associates
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
