Dears, I'm an old programmer and would like to know the answer, too. To my point of view, on-line programs(or you may call them user interactive programs) is just another side of an application. There are still a lot of things that the application should take care of which requires no user interactions at all. Unfortunately, web applications focus more on user interaction only nowadays. It looks like "backgroundrb" is a running environment designed for batch jobs. >From the OS's point of view, the "backgroundrb" is just a different process from the web server. It seems that they create "backgroundrb" to accept "submit jobs" commands from the web server running rails. And those long-running batch jobs(which requires no user interaction) can works well without impacting on-line transactions served by rails. Or, I may say that It's more like a queuing facility for rails. Heroku, as a playground of web applications, do they really allow us to run "backgroundrb"?
Mega On Apr 18, 10:57 am, "Sarah Mei" <[EMAIL PROTECTED]> wrote: > The typical way to do stuff like that is to write a rake task that you > run at the command line (or via cron), but I'm new to Heroku and I'm > not sure how they handle the running of custom tasks. I'll leave that > to the Heroku experts. :) HTH. > > On Thu, Apr 17, 2008 at 6:46 PM, cmk <[EMAIL PROTECTED]> wrote: > > > I'm a long time developer but new to ruby, rails, heroku, and, in > > fact, web applications in general. I'm trying to create a background > > process to do tasks outside the normal request/response cycle. [...] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
