2010/3/8 Joe Martin <>:
> Robert Klemme wrote:
>> Which other method are you referring to?
>
> Well my original thinking was to create a thread for every single item I
> pass to the program. =A0Caleb answered this for me in that threads
> themselves are quite heavy, so it further leads me to go with your
> solution which creates a low number of threads and re-uses them until
> the queue is empty. =A0It seems much more simple and effecient than my
> original plan.
Ah, OK. Then I was just confused because you had used the term
"thread pool" in your original posting. That term is commonly use for
exactly the type of solution I posted (fixed or at least limited
number of threads which get their tasks from some form of queue). You
probably weren't aware of this.
Kind regards
robert
--=20
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/