search for: backgrounddb

I have a bunch of real uses for BackgroundDrb, but I also a very simple need to delay sending an email for about 5 seconds after a rails action completes. Basically I need to leave time for the DB to commit and sync to the slaves before the email can be sent Is BackgroundDb the right tool for this job? Any other suggestions on ways to implement this? (I have seen suggestions to create a new thread and run the mailer from that thread, but it''s not clear that actionmailer is actually thread safe..?) I''m thinking just to fire up worker threads whi...

...made) 4. Run my Net::HTTP.get_response(), which takes from 0.00001 to 600 seconds to complete. 5. Write output to some log file. What''s gotten me into trouble now, is I want to do touch the database. Which creates all sorts of havoc in rails when threaded. I''m pondering using BackgroundDB, but it looks like it''s meant for slow running tasks, not thousands of messages flying back and forth. I was also thinking of, not touching the database in the thread, but posting the results back to a separate instance of the rails app, and let that instance handle the writes to the data...

Here''s a gedanken experiment for those w/ far more knowledge than I about ActiveRecord, etc.: Let''s say my database is very remote and on a very slow machine. Let''s further say that my app has an action that leads to a very simple insert into the "impressions" table of the db, a la "INSERT INTO impressions(docid) VALUES($docid);" - and