search for: emarceta

Hi there, We''ve been using previous version of bdrb (drb based one) for a while and it was running relatively OK. We recently attempted to upgrade to the new version to keep up / use supported version but we ended up reverting to the older version. Here are the things that moved us to revert : 1) With the workers we never manage to pass this error: '''' You have a nil

Hi there, In the latest releases bdrb attempts to load all models during startup routine. We have models that depend on the particular RUBY_PLATFORM but they live in the same models directory. It seems that the inability to load them stops bdrb. Could the models requiring / loading be done one demand, the same as Rails does? thanks, emil

Hi there, We run several (3-4) Rails servers behind the reverse proxy / load balancing web server serving the single application. All Rails instances share the same database and use the database as a session storage. Memcached is also part of the picture. I''m looking into using Backgroundrb for some large uploads / parsing task that provide progress status updates (via ajax calls).

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

Hi there, This is in master_worker.rb at 266 - it looks to me that there is a bug in reading the lazy_loading property. The line below doesn''t work if lazy_load: true is specified in the yml. lazy_load = CONFIG_FILE[:backgroundrb][:lazy_load].nil? ? true : CONFIG_FILE[:backgroundrb][:lazy_load].nil? should say something like this: lazy_load = CONFIG_FILE[:backgroundrb][:lazy_load]