>> >> The problem is when your threads are named dynamically, >> >> there's no way to >> >> reliable get the thread name. >> > >> >What about using evaluate(), or thrd["#i#"], or >> ><cfset "thrd#i#" = ...>? >> >> The problem is the variable "i" can be read/written to from any of the >> spawned threads. This means the value of "thrd#i#" won't >> always correlate to >> the actual thread number (since it's evaluated inside the >> thread, inside the >> loop, the value of "i" keeps changing.) > >Ah, I get it now. So just don't use any variables in your threads! ;) >But seriously, I'm sure when/if they release this in a product release, >there will be solutions for this problem.
I know the first part was a joke, but I did want to clarify a bit. Well, it's not that you can't use variables--it's just that you've got to be very careful in *how* you use them. If you were wanting to create 3 simultaneous requests that each did they're own thing, you have no problem doing that now (as long as you don't reuse variables between these tasks.) However, I think that a lot of people will want to spawn off tasks based upon some kind of loop (i.e. resize a bunch of uploaded files, update several records in a database, etc.) This is where things are lacking right now. The good news is, I know they're listening to all the feedback (I do know this for a fact) and looking to implement some changes to the code base to address the shortcomings. I suspect we'll see another release in the not so distant future. -Dan ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:247400 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
