This seems to be a somewhat common use case for Heroku: I have a process that takes far too long to tie up a web request but doesn't happen often enough to warrant paying for a Worker.
Right now I'm considering calling fork to handle this situation and I have two questions: 1. Will this work on Heroku? That is: are there any specifics about the Heroku architecture that would prevent forks? 2. Is there a better way that doesn't involve having a Worker running all the time? I've seen people mention that Workers can be spun up and deleted programmatically but I've yet to see what the API for doing so looks like. Thanks, Gabriel -- 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.
