Aníbal Rojas wrote: > Alex, > > I would strongly recommend reworking your code to execute your > long running actions in a separated thread. This way you will prevent > that every Mongrel gets busy with long running threads and your > aplication becomes unresponsive. > > There are different ways to handle Rails long running threads, the > simplest is to spawn a new script/runner process, also you could use > BackgroundDrb: > > http://backgroundrb.rubyforge.org/ > > Best regards,
I knew that was an option, but this is a somewhat old rails app at this point for an old client. I was trying to avoid spending this refactor time, hoping that mongrel + pound could handle this as elegantly as lighttpd + fcgi did. There is also the added issue that the long running action writes to the session periodcally to update the user on its process. This would not work with Drb or script/runner since there is no session there. I guess I can write it to a file, and read that in. But it's work I was hoping I wouldn't have to do. Thanks for the tips -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Deploying Rails" group. To post to this group, send email to rubyonrails-deployment@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-deployment?hl=en -~----------~----~----~----~------~----~------~--~---
