search for: query_all_workers

What does the method query_all_workers() do? There is no documentation on what this method returns (1.0.1 version). Orion -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080118/9f9b8112/attachment.html

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

...doing in my rails console. MiddleMan.new_worker(:worker => :foo_worker, :job_key => ''1'') worker = MiddleMan.worker(:worker => :foo_worker, :job_key => ''1'') worker.bar() Querying all workers shows the foo_worker_1 is there.. >> pp MiddleMan.query_all_workers {:type=>:all_worker_status} {:log_worker=>nil, :foo_worker_1=>{:rand=>679}} I''m using rails 2.02, Packet 0.1.5 and Chronic 0.2.3. I tried the mainline git version but got this error. It needs a newer version of Packet? `load_missing_constant'': uninitialized consta...

Is it expected that MiddleMan.ask_stats will return a status for a worker that has been MiddleMan.delete_worker''ed? The worker isn''t showing up in MiddleMan.query_all_workers, so it seems that is shouldn''t have a status either. Is there a way to define a callback that is called at deletion, to reset the status, or do I need to write my own method to reset the status before I delete the worker? TIA -todd[1] -------------- next part -------------- An HTML attac...

...e? 4) I want to be able to monitor current status After the pattern of Linux daemons, I''d like to be able to run "./script/backgroundrb status" and get my status back. I can submit a patch for this if anyone else is interested. However, I noticed while writing that patch, that query_all_workers() seems to be broken in the trunk r302 (status for all workers is always nil). So my workaround for now is to use ask_status(): t_response = MiddleMan.query_all_workers t_response.each {|k,v| puts "#{k}: #{MiddleMan.ask_status(:worker => k)}" } Anyhoo, that''s it....

...s available for MiddleMan, etc. Right now, I''m trying to figure out how to get a list of all running workers. Poking through the source code, I see a function entitled "get_worker_by_class", but there is little to no documentation available. The documentation does refer to query_all_workers, but I can''t find it anywhere in the source code. I understand that cool technologies often race ahead of the documentation writers. But am I misunderstanding something? Perhaps I''m looking in the wrong place? Thanks, Norman Elton

I''m running the latest from svn (rev 285). I''ve been having a problem launching a process repeatedly. What happens is that I get a debug message "some read error" and then the worker refuses to run again. I''ve stripped my worker down to just doing a puts and it still happens. Like the other threads I want to launch my workers as needed, however I get the

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