June 2011 ACFUG Meeting
Date
Wednesday, June 1, 2011
Dinner &
Running into a headscratcher with cfthread. CF 8 Ent, Win 2k3
This works:
this throws an error "Element THREAD1.MYVAR is undefined in REQUEST":
What gives? How do I prevent scope hunting when referencing the result of my
threads?
Thanks!
Mischa.
Can threads be referenced with the request scope?
Troy Jones
[cid:image001.jpg@01CC1AF4.D22D5370]
___
Troy Jones | Director of Technical Services | Dynapp Inc | 1-800-830-5192
ext. 603 | dynapp.com<
That's another way of phrasing my question :-) Stuffing them into a struct
works, so it's not some sort of issue w/ dot notation
works.
From: t...@dynapp.com
To: discussion@acfug.org
Date: Wed, 25 May 2011 15:00:08 -0500
Subject: RE: [ACFUG Discuss] CFThread name issue
C
I'm thinking that when you send something to thread, you have divorced it from
the request scope entirely, hence, your inability to reference it as a request
scope variable even with a syntactically correct var name. Based on what you're
posting, I'd say scoping it into variables would solve the
I think this is more about naming the thread itself than passing values into
it. Let's say I'm not interested in passing values in, or even the outcome of a
thread, only how much time it took:
This took #thread1.ElapsedTime# ms.
How would I code the above and have CF *not* hunt for
