> Let's say I declare a series of CFthreads on a single page. These will
> process serially, not concurrently, right?
Yes.
> What if one fails? Do the subsequent threads die with it, or do they continue
> to process
> after the failed one craps out?
Each thread is a separate program. The failure of one will not affect
the others, unless they're accessing a shared resource which is
blocked by the failed thread (which is generally unlikely).
> And, is there a way to control/choose either of these behaviors?
Not directly, but you can certainly do this sort of thing indirectly
by writing monitoring code. There's an example of this in the last
version of the Advanced ColdFusion course that we wrote for Adobe. In
a nutshell, threads can sleep and wake up, expose their status, and
you could read that status in another thread. You won't be able to
tell that a thread has "failed", but you could tell that a thread is
still busy, and make an assumption that a thread that's been busy for
too long has failed.
Dave Watts, CTO, Fig Leaf Software
1-202-527-9569
http://www.figleaf.com/
http://training.figleaf.com/
Fig Leaf Software is a Service-Disabled Veteran-Owned Small Business
(SDVOSB) on GSA Schedule, and provides the highest caliber vendor-
authorized instruction at our training centers, online, or onsite.
~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive:
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:359902
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
