Wouter de Bie wrote: > I wouldn't run a long running process directly from your controller, > since rails first renders all stuff that should be sent to the client > (html/xml/js/etc) before it actually sends it. This means that the > complete controller action should be finished to show something in your > browser. > I think that the best way to go is to use something that is able to > spawn background processes (like Starling).
I'm aware of different solutions to run a background job. However, the problem is how to make 4 background jobs MPSAFE, all of them working on the same Hash. Any ideas? Petr -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
