search for: sweiss

...do_work worker_methodprocess_batchtypedo_work You have a nil object when you didn''t expect it! The error occurred while evaluating nil.send_request /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5/lib/packet/ packet_master.rb:44:in `ask_worker'' /Users/sweiss/Documents/workspace/RACE-local/vendor/plugins/ backgroundrb/server/lib/master_worker.rb:104:in `process_work'' /Users/sweiss/Documents/workspace/RACE-local/vendor/plugins/ backgroundrb/server/lib/master_worker.rb:35:in `receive_data'' /usr/local/lib/ruby/gems/1.8/gems/packet-0.1.5...

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

Hi, I''m not much of a developer but I''ve been using backgroundrb for a while now and with the release of 0.2.1 it looks like I can finally upgrade from the old version (0.2.0 had some weird issues when jobs just wouldn''t run, seems to have cleared up now - Thanks!). Anyhow, while I''m doing this, I would like to tackle this problem. Most tasks I run in

Hi, This is a patch that allows you to work with multiple backgroundrb servers from within Rails. It modifies the rails worker proxy to use a middleman supplied in its constructor, instead of using the MiddleMan constant. Basically a fix to make BackgrounDRb::WorkerProxy.custom_connection usable (without patch, you can establish a custom connection but all calls to worker objects

Hi Bill, I have "version 1" backgroundrb running on my development server with rails 1.2.1, with no issues (other than the left over DB connections blocking up my MySQL server, which isn''t exactly a new problem). Going to move production servers to rails 1.2.1 very soon, I''ll post back if there''s any trouble. Still would *really* like to get version