If possible, can you send diff against git master, which has little light
weight implementation of thread pool tasks?



On Mon, Apr 20, 2009 at 9:02 PM, Fitzhugh, Cary <[email protected]>wrote:

>  Hi all –
>
>
>
> I modified background rb so that when you enqueue tasks it will take
> advantage of your thread pool.  Right now, it will only select 1 job from
> the queue at a time.  And using all defaults, that is one job a second.
>
> I’ve modified BDrb_Job_Queue to allow you to request more than one task
> from the queue – it returns an array or an item (if count == 1).  And then
> in the meta_worker, it has a few mods to allow you to invoke all those jobs.
>
>
>
> I’ve attached my svn diff for people to look at – I don’t know if this is
> all that useful to others, or if it is a good idea. I can’t see why not –
> but I’m new to this project.
>
>
>
> If someone wants me to do more with this diff let me know.
>
>
>
> Thanks,
>
> Cary
>
> ------------------------------
> This e-mail and any files transmitted with it may be proprietary and are
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this e-mail in error please notify the
> sender.
> Please note that any views or opinions presented in this e-mail are solely
> those of the author and do not necessarily represent those of ITT
> Corporation. The recipient should check this e-mail and any attachments for
> the presence of viruses. ITT accepts no liability for any damage caused by
> any virus transmitted by this e-mail.
>
> _______________________________________________
> Backgroundrb-devel mailing list
> [email protected]
> http://rubyforge.org/mailman/listinfo/backgroundrb-devel
>



-- 
Let them talk of their oriental summer climes of everlasting conservatories;
give me the privilege of making my own summer with my own coals.

http://gnufied.org
_______________________________________________
Backgroundrb-devel mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/backgroundrb-devel

Reply via email to