search for: no_auto_load

Hi there, Just a small suggestion : The following apis could be a bit more concise / shorter / pleasant I thought. This is particularly difficult, my brain stumbles on this each time when scanning thorugh the code :) set_no_auto_load(true) Could it be two apis instead? auto_load no_auto_load and the other one : worker_name :important_worker (no set_ prefix) thanks, emil

...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 same behavior whether use the auto_load and ask_work or use new_worker with no_auto_load. If I remove the job_key I can get it to work, but I still get the "Some read error" message. I need the job to keep one worker per id. I''d rather have separate processes than go the thread route - for now. class UpdateFacebookAccountInfoWorker < BackgrounDRb::MetaWorker...

I tried to upgrade my existing application to RC2 last night. Like many, I use this mostly for running scheduled tasks. For the moment, I''ve abandoned the effort, but am looking forward to being able to use this. Feedback below: First, the reason I was looking forward to this upgrade was to use the threaded scheduler. I have an application with long-running tasks. I found that