search for: worker_info

...how many requests you send to the worker, they all will be queued in a thread pool, but since thread pool is of size 1, only one of the task would run at a time. You don''t have to worry with thread issues, because only one thread will at a time anyways. 2. I have a method called MiddleMan.worker_info, which can be used like this: >> MiddleMan.worker_info(:worker => :rss_worker) => {:status=>:running, :worker=>:rss_worker, :job_key=>nil} You can pass some job_key also to check whether a worker is running or not. If a worker is not running, :status value will be :stopped....

I have a worker which wants to delete itself after it finishes its work- how can it do that? Best Regards, Danny Burkes

...essage debugging can be disabled now with ''debug_log'' option in configuration file( :debug_log: false) * Use lazy load (:lazy_load: true) of models in master * MiddleMan.delete_worker aborts a worker immediately now. * Get information about all running workers. ( MiddleMan.all_worker_info) * Enable setting of thread pool size. Tasks can be queued easily now. * Introspect a running worker ( MiddleMan.worker_info, note that this is different that MiddleMan.ask_status, since later will return status objects set by you in worker code) * Removed messing around with Core classes. Backg...

I''ve been using backgroundrb since back in March 2007 or so. It''s been working mostly OK for me, but since the old version doesn''t seem to work out of the box with rails 2.0 for me, I decided to test out the latest version. So, I''m looking at the scheduling, and trying to figure out the best option for what I want to do. What I have is a set of workers that

Hey all, Below is a proposed patch I worked on over the weekend. Just adding a note here to mention that I''m currently not a subscriber to the mailing list, so please CC me on any replies. Let me know what you all think. This change was made on a local topic branch off of the maint branch. If you''d like to view the change on GitHub, you can do so here: