similar to: Update your packet gem for Mac OS X issue

Hi Folks, Well, Yesterday I pushed some more updates that I was cooking since last couple of days. Here is a brief list: 1. Results from worker stays even after a worker dies. 2. You can ask backgroundrb to store status objects in memcache cluster now. by default its stored in master process memory, but I have introduced an option to allow it to be stored in a memcache cluster:

Hi, I am pushing some updates and fixes that addresses much of the issues that we talked about since last couple of days. 1. Use configuration option :debug_log: false to disable backgroundrb_debug.log. 2. As shown below, use lazy_load option to disable aggressive loading of models ( and somewhat stupid too). 3. MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the worker, it

Hi , If you are following commits, I have pushed following changes: 1. Now, you can specify :environment option in config file to load production environment and stuff. 2. Exeptions that were exposed to the user has been changed to BdrbConnError if rails is not able to connect to bdrb server. 3. loading mechanism has been changed, so remove backgroundrb script from your backgroundrb directory

Hi All, One can easily code a backgroundrb worker so as it can act as a worker queue, having reached a stable status, perhaps its time we should add this feature. Why? Because if you are already running your application using BackgrounDRb, perhaps you don''t want to manage other solutions when capability to do that is right there with you. Interface? This where i need feedback. You can

Hi Folks, I am glad to announce 1.0 release of BackgrounDRb. This would be a major release since 0.2 release of BackgrounDRb. Here is a brief summary of changes: - BackgrounDRb is DRb no longer. It makes use of EventDriven network programming library packet ( http://packet.googlecode.com ). - Since we moved to packet, many nasty thread issues, result hash corruption issues are totally

Hi, Ok, As i promised.. I am working on new version of BackgrounDRB, which is getting close and will be out soon. I need some feedback from you guys. So, please reply back. The code has changed significantly and its no longer using DRB. But I will keep the name BackgroundRb. Ok, in new API, a worker looks like this: require "net/smtp" require "guid" class NewsletterWorker

Hi, A pre-release version of backgroundrb is available now from svn. Download it from here: http://svn.devjavu.com/backgroundrb/branches/version099/ Since this release marks significant migration from existing practices, i intend to keep trunk untouched for a while. There are no install scripts, but you should copy "backgroundrb" file from script directory of plugin to script

Hi Folks, Troll trumps your existing ActiveResource mocking libraries like inbuilt HttpMock,Fakeweb or Webmock out of water. With Troll, ActiveResource mocking just works, some of its features: 1. Don''t need to mock calls at Net::HTTP level (which webmock,fakeweb do). Really, we don''t care what HTTP library ActiveResource uses, fakeweb and webmock bring additional complexity

Hi Folks, I am glad to announce a 1.0.1 release of BackgrounDRb library. It has numerous fixes and some nice feature updates, so please upgrade. Code: http://svn.devjavu.com/backgroundrb/tags/release-1.0.1/ Updates and Fixes: * Fixed issue with Mysql Lost connections * Message debugging can be disabled now with ''debug_log'' option in configuration file( :debug_log: false)

Hi Folks, Thanks for your patience, new release of BackgrounDRb is available now. You can get it from here: http://svn.devjavu.com/backgroundrb/trunk/ Yes, older version is deprecated and not supported anymore. A brief list of changes since last release is: 1. Now, each worker has logger objects, which can be used to log stuff. 2. A worker can be started or scheduled dynamically. 3. Multiple

1. Whenever you ask BackgrounDRb to perform a particular task using: MiddleMan.ask_work(:worker => :rss_worker,:worker_method => :fetch_url, :data => "www.google.com") Your task would be performed then and there. But, if your worker is busy, task won''t be queued, except in socket buffer. And your request may get lost. This isn''t generally a problem

Hi, 1. Is there any particular reason to not return ActiveResource objects when calling custom methods on Resources? Currently depending on request type, ARes returns hash or Net::HTTP::XXX responses. 2. I think know_attributes should be inheritable between ARes classes. Is there any reason to not do so? 3. custom methods can''t be directly overridden in plugins via modules, because

Hi Folks, BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be used with Ruby on Rails applications for offloading long-running tasks. Since a Rails application blocks while serving a request it is best to move long-running tasks off into a background process that is divorced from http request/response cycle. This new release of BackgrounDRb is also modular and can be used

Hi, just updated backgroundrb to release 1.0.1 and am getting this error when trying to start backgroundrb. vendor/plugins/backgroundrb/framework/core.rb:18: uninitialized constant Packet::ClassHelpers (NameError) Just updated from r298 where everything was working fine. If I comment out the offending line then backgroundrb starts but I can''t connect to it from my app. Anyone have any

Hi, all. Just wondering if anyone has tried using the Paperclip file upload plugin with Backgroundrb. My current implementation uses attachment_fu - I save the file initially to the file system without generating thumbs, then a bdrb process picks up that file, generates thumbs, and saves to S3. This works fine and dandy, the only hitch is I want to save image metadata in the same table

Hi Folks, We are glad to announce shiny new release of BackgrounDRb, which will soon become 1.0. A quick summary of changes: - BackgrounDRb is no londer DRb, its based on event driven network programming library packet ( http://www.packet.googlecode.com ) . - Since we moved to packet, many nasty thread issues, result hash corruption issues are totally gone. Lots of work has went in making

Can anyone explain why BackgrounDRb is switching form DRb to SMTP protocol? That seems like a lot of overhead to add to the messaging back and forth? Orion

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

I''m getting the following error (when doing script/backgroundrb start) on my local machine, which is running os x 10.4.11. However, it works just fine on my linux server. RAILS_ROOT/vendor/plugins/backgroundrb/lib/../framework/nbio.rb:64:in `dump_object'': undefined method `write_nonblock'' for #<UNIXSocket: 0x135b5f4> (NoMethodError) I just grabbed the

is there an easy way to disable logging to backgroundrb_debug.log? Regards - reynard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20080102/195dee18/attachment.html