Are you seeing this behavior while running your rails app under a typical development environment setup, ie a single mongrel instance of the dev env running? If so, then the blocking/hanging is due to the fact that your archiving meth is trying to make an httpclient call (using wget) back into your single-thread/-process rails app which can only handle one request at a time.
If this is the case, you'll need to setup/run a second instance of your dev env (or launch your archiving meth via script/runner, or setup your dev env to run under mod_rails/passenger, or ...) specifically to handle your archiving httpclient requests. Jeff On Apr 21, 5:29 am, Carlos Santana <[email protected]> wrote: > Thank you Jeff. > > How can I do it without blocking any other requests? I tried to do this > multi-threading with no success (got into infinite loop condition). > > Also, I read that while running background system commands it is good > practice to start new fork rather than a new thread. This gives us more > control over the code. > > Is there anyway to run this background process without blocking other > requests and also get to know it's completion status? > > Any help appreciated. > > Thanks, > CS. > > Jeff Burlysystems wrote: > > One way you could do it: > > > # in your model meth: > > -- > Posted viahttp://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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
