search for: all_worker_info

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

I''ve been using backgroundrb for... about an hour now. I must say, I''m impressed. But I''m a bit stumped on where to find the "official" documentation. There''s an API online at backgroundrb.rubyforge.org, but I don''t see the methods available for MiddleMan, etc. Right now, I''m trying to figure out how to get a list of all

Hi, I''m trying to silence the information that backgroundrb is putting in to my test runs. I''m seeing several hundred lines of this during the test runs (both unit and functional): {:type=>:all_worker_info} {:type=>:do_work, :worker=>:xmlrpc_xmpp_worker, :worker_method=>:register_user, :data=>{:xmpp_password=>"04ced0eda236a8690ec8ed30af63b3f2d886109c", :userid=>1151}} but can''t find where it seems to be coming from. How do I shut it off? I''m using 1.0....

.... MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the worker, it won''t wait for tasks to finish. I am still skeptic about the behavior, but since that was the behavior in older version, I am continuing it. 4. Get information about all running workers: >> MiddleMan.all_worker_info => [{:worker=>:log_worker, :status=>:running, :job_key=>""}, {:worker=>:foo_worker, :status=>:running, :job_key=>""}] --- :backgroundrb: :port: 11006 :ip: localhost :environment: production :log: foreground :lazy_load: true :debug_log: false...

...;'s 2.0 version, I''m using the one that didn''t really have a version number). The 2.0 version did very little but crash for me. Anyway I finally got some time set aside to try out this new version you all have been developing. I''m very excited about the new all_worker_info method on MiddleMan! It should drastically improve the way my users can manage their background processes. Unfortunately, I can''t seem to get even the most basic worker to do anything. I followed all the instructions for installation, and installed from SVN (I''m on OS X...

...* Message 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...

Hi, Thanks for the help getting the new backgroundrb working, things are working fabulously now. I have two questions: 1) I have a few basic methods I need available on all my workers in order to communicate properly with my application... it seems to make the most sense right now to subclass BackgrounDRb::MetaWorker, or make a mixin module, because I''m actually extending some