similar to: Rails and background tasks/threads

Folks- I just commited another revision of the plugin. Nothing huge in this update but some extra features. Acl lists are now configurable in the config file. So you will want to blow away and recreate your config file again. Thanks to Georg Friedrich for this. And I applied Gunter Ladwig''s patch for singleton worker classes. These are workers that only have one instance of

Is it possible to make the process priority higher for backgroundrb? Thank You, Ben Johnson E: bjohnson at contuitive.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060819/7a2e6d1b/attachment.html

I have a very strange problem here. I do not get this. So any help is greatly appreciated. Basically I have a model that calls a method in the background process in the "after_save" method. Let''s call the model products. So what happens is this: 1. I create a new product. 2. Everything works and the product is saved with id 13. 3. A method is called in my background

My application is going to have a work queue of scheduled tasks stored in the DB. This work queue will be shared across multiple Rails app servers. I need a way to ensure that no two servers get the same jobs if multiple servers pop jobs off the top of the queue simultaneously. Is there a fairly simple way to acheive this? Or do I need to come up with some fancy secondary server to dispatch

Hi all, I have an external web service that I need to log into at a specific part of my web app,. The problem is that I only have one login to this web service, and if another login attempt is made while an existing login session is still active, the existing session gets terminated. How can I best serialise access across my mongrel cluster to this external API? I thought of creating

Hello, Thank you so very much for Backgroundrb. Good Stuff. A general question: Do: - calling ''teminate'' within a worker - calling delete_worker through MiddleMan - letting the :ttl expire - calling MiddleMan.gc! (with an appropriate timestamp) All accomplish the same thing? And here''s a bonus feature request: It''d be cool if you could specify how many

I have looked through the docs, looked at the code, even gave a cursory (2 page) glance at google, and it is not clear to me what SpecServer is or what it is for. Is it meant to speed up the execution of specs in a rails environment by doing some magic on the database? Or I am thinking it keeps a copy of Rails running to avoid the rails reload delay... Is there any documentation on this so I

I''m developing a stateful Ruby application that needs to keep data in one location where all people accessing the site can modify its contents. This data will be read-from/written to often, so I would prefer for rails to keep it in memory, rather than a database. My frist try involved global variables. After discovering that they were being "re-initialized" with each new

In response to my Rails Weenie post today[1], someone mentioned that I try BackgrounDRb to help take the strain off my application. 1: http://rails.techno-weenie.net/question/2006/7/13/nested-loops- best-way-to-send-messages-to-blog-subscribers I''ve just tried to install and use BackgrounDRb with my app, but I''m afraid that I''m not too versed in running processes

Just received the news from Tom Mornini. Congrats Ezra for the new Engine Yard site and the blog you will be collaborating. Hope to read you there soon. http://www.engineyard.com/ Jonathan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20060925/3f251fa4/attachment.html

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

so i have an after_create method on my track model that kicks off a background process that converts an mp3 to a swf. this is working fine locally on my machine, but upon moving it to my production server, i am getting the following error. I''ve only been using backgroundRB for like 48 hours, so i''m not really sure what this means or where to go. any ideas?

I want to use DRb within my Rails app. Right now I''ve got a very basic class: class PaymentGateway cattr_accessor :ssl_config, :host, :port def self.gateway @@gateway ||= new end def process(amount, card, type = :auth) @biller.process(amount, card, type) end def set_card(user_id, number) @biller.set_card(user_id, number) end protected def initialize

In our app we''ve a number of singleton ruby classes that cache static data in hashes, things like string values, system config params, etc). In a webbrick environment this works ok, but we find in production we have a problem because we have 4 caches, one for each mongrel instance. This also isn''t a BIG problem, but our cache.reload() methods are kinda useless now, because we

I''m using backgroundrb for session management and deletion of visitor-entered information when a session is abandoned. The visitor can either click a button to end their session and remove their data, or backgroundrb will do it for them after 5 minutes of inactivity. Everything''s working fine, I think. If the visitor explicitly logs out, then when the worker checks for their

Friends- I''m happy to annouce the first alpa release of BackgrounDRb. This is a small framework for managing long running background tasks that allows for ajax progress bars and more. It also serves as an Application wide cache and context store for when you need something like sessions but shared between users and multiple backend processes like fcgi''s or mongrels.

I''m trying to get Merb running on Windows XP SP2 and am experiencing some difficulties. I load http://localhost:4000/posts/new in my browser expecting to see the contents of new.herb rendered. However the following error is reported: Request: PATH_INFO: /posts/new Params: {"action"=>"new", "id"=>nil, "controller"=>"posts"}

Can''t believe I can''t see the problem here, but after a few hours bashing my head on a brick wall, going to risk looking stupid by seeing if anyone can point out my idiocy (that''s the worst thing about coding on your own). Trying to get BackgrounDRb to take over the scraping task which is currently being done in a Rails controller. That''s not the problem at

Hi, Is there any interest in allowing controller methods to do post-response processing? This would be useful where some time-consuming statistic or index processing should be done after the response has been sent so as not to delay a response that does not depend on that processing. This could be implemented by allowing the action method to yield to the process method which in turn yields to a

I''m having trouble getting backgroundrb up and running in a production environment. Here''s my backgroundrb.yml: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: XXX.XX.XXX.50 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 XXX.XX.XXX.51 order: deny,allow I start BackgroundRB from XXX.XX.XXX.50 with