Just thinking, your scrape should probably be in a worker, stick the results in a db, Depending on what your using, you configure it to be a temp table even. Then in your search window you can do ajax based updated from the scrape. With the ability to then clear up the cache. You get more concurrency, and with the right javascript you could cancel the scrape in process.
Think this would scale and be more responsive On Apr 5, 10:02 pm, Adam Akhtar <rails-mailing-l...@andreas-s.net> wrote: > Excellent thanks once again Andrew! Appreciate your advice. > > -- > 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 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 -~----------~----~----~----~------~----~------~--~---
