similar to: Ezra''s Call For Help...

In a previous email you wrote this: Glad you''re getting some use out of the plugin ;) ActiveRecord does have some issues with threading and concurrency that can sometimes cause that error you are seeing. Open up your script/backgroundrb/ start file and comment out the following line: ActiveRecord::Base.allow_concurrency = true Make sure you do that up in your main app script folder

Is there something special I need to do to access session data in a worker? I''m using an AR session store. I''ve been working with Ezra''s tutorial, modifying it a little here and there to figure it out. So I changed the progress bar to a simple count-down in the worker which sends back the count to display in the view. No big deal. But if I try to access session

Hey Greg- Yes I am sorry, the new architecture uses fork and named pipes and a bunch of unix stuff to do its magick. Now you may be able to port it to qwork on windows, but I don''t think it is possible :( I''m really sorry about this but I need this thing to be as robust and solid as it can be and in the end windows isn''t compatible. Now you may be able to

Hi all, In the recent Advanced Rails Recipes book, Ezra states that Rails needs a little bit of adjustment for its restful routing to work with Facebook. He suggests created an initializer named facebook_overrides.rb and adding this code: http://pastie.caboo.se/206696 But I was just testing restful routing without that code, and Rails seemed to be working fine with Facebook.

On Jul 18, 2006, at 6:24 AM, Matt Mower wrote: > Hi Ezra, > > I''m converting some code I have which basically ran Enumerable#map > asynchronously using a thread-per-value to use backgroundrb > (recommended by zedas). That code works but I have a scaling problem > and needed to introduce throttling. > > However now that I''ve looked at it I don''t

Ezra, Suppose a chatroom application, a RailsApp + 2 backgroundrbs: MiddleMan1& MiddleMan2, running in 2 machines. When Chater1 login, RailsApp call MiddleMan1 to get something about Chater1 from db to memory, like his contacts or other personal settings. When Chater2 login, RailsApp call MiddleMan2 do the same thing. But who is reponsible for the Global Data? like a Online Chaters

Begin forwarded message: > From: Ezra Zygmuntowicz <ez at brainspl.at> > Date: June 29, 2006 8:18:10 PM PDT > To: Douglass Turner <douglass.turner at gmail.com> > Subject: Re: [Backgroundrb-devel] Need to send email from a worker > > > On Jun 29, 2006, at 7:45 PM, Douglass Turner wrote: > >> Hello, >> >> Can someone suggest the simplest way to

I''m trying to use BackgrounDRb to do image processing on large uploaded zip files of images, but $script/plugin install svn://rubyforge.org//var/svn/backgroundrb gives me this: /usr/lib/ruby/1.8/open-uri.rb:88:in `initialize'': No such file or directory - svn://rubyforge.org//var/svn/backgroundrb (Errno::ENOENT) I can install the old version with $script/plugin install

Hi all, BackgrounDrb was exactly what I needed for a project I''m working on at work. Everyone''s really impressed, and now it''s time to put the system into production. My question is, how do I avoid having to manually run the startup and shutdown scripts (or the rake tasks) for backgroundrb? I tried putting a system "rake backgroundrb:start" in my

First off, Ezra, thank you for putting out BackgrounDrb. Looks like a very useful framework. I have a newbie question about ruby threads. Are there any general things to avoid doing when using ruby threads and rails? Also specifically, will using BackgrounDrb avoid the socket problem described in this link (extracted from Rails wiki):

Hi Ezra, Thanks for the great work on BackgrounDRb. I have come across a couple of problems. 1. I wanted to define a simple class in the worker file to wrap up and pass back some data to my controller. It seems that if I create the class either inside or outside of my worker class (in the same file) it gets wrapper by a DRb::DRbUknown object and therefore cannot be accessed from my controller.

Hello, Bravo Ezra for Backgroundrb! What an elegant piece of engineering. I envision many folks like myself looking at our CPU hogging executables and finally seeing a clean path to the Web. I was wondering if any folks have a good strategy for calling out to a C++ (or any other compiled) executable from a worker. Is the only option to call system() from a worker? That feels a bit unsatisfying.

Hi all, I just read Ezra''s article on BackgroundRb and decided to use it one of my projects. I installed the plugin into my rails project using script/plugin and then ran rake backgroundrb:setup to copy the yml scripts. Now my backgroundrb.yml looks like ======= --- port: "22222" timer_sleep: 60 load_rails: true environment: development host: localhost database_yml:

> On Jul 30, 2006, at 5:11 PM, Chris H wrote: > >> Hi Ezra, >> >> thanks for the reply. >> >> There''s a ruby process that appears in top when I fire off the do_work >> method. >> It uses around 30-50% cpu and disappears once all processing has >> completed. >> >> When I try to stop processing using delete_worker I was

Hi there, as i stated before in my talk with Ben Johnson, I hacked a little bit and here it is - autostarting jobs. I think someone (eh... Ezra) should review it and check to see if i made any mistakes. Also i dont have the possibility to test it on other-than-Windows systems, but since the calling process works just the same, it should do well... Now the neccesary evil, the documentation... If

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)

I''m just getting started wtih backgroundrb, and unfortunately hit a snag right away... I''m running the latest releases of rails, backgroundrb, slave and daemons. I created a simple worker class, using the generator, which currently does nothing but print the arguments that are passed to do_work. I''m running backgroundrb using ''./script/backgroundrb

Hi all, I am using the LoginGenerator and Ezra''s acl_system2 to protect certain actions in my controllers. I have written some functional tests to check for correct handling of redirects, flashes, etc. The flashes however only get populated on the first get action in any given test. Here is what I have so far: In the controller: class PageController < AC before_filter

Hi, First off, thanks Ezra for showing the way with BackgrounDrb. It''s a real godsend. I wanted to add a bit of job control to the system so that I could cancel DRB processes and so on. I thought I''d share how I did it in case anyone should find it useful or have feedback. I wanted to be able to put checkpoints into the drb job so that I could let the job do whatever needs to

It''s that time again friends. skaar has been at it again and has greatly improved the stability of the new system. And Ara Howard has helped a ton by working with us on the slave library to iron out the wrinkles./ The results is a lot nicer backgroundrb for everyone. I have to say another huge thanks to skaar. He has singlehandedly wrote almost all of this new version and many