Hello there Pierre, Threads are not really threads in ruby, so forget about threads.
Instead use a background process for that. You can accomplish that using some gem for creating background processes. Delayed Job may be a solution for you. []'s Rodrigo Dellacqua On Sun, Jan 10, 2010 at 7:52 PM, PierreW <[email protected]> wrote: > Hi guys, > > I need my app to make a few hundreds requests to external web services > as quickly as possible. The web services are fairly fast, but still: > if I do the requests one after the other, it is too slow. > My understanding is I have two options: > a- Threads. > b- Typhoeus > > Typhoeus seems great. Yet, the web services are all quite different > (some are SOAP, some REST...) and therefore wrapped into interfaces. I > might be able to implement Typhoeus but it means a lot of changes. > I have read that threads in Rails can be challenging to implement > especially when dealing with the DB. Yet, this part of my code doesn't > do anything with ActiveRecord. Are threads generally "OK" if no > connection to the DB is involved? > > Thanks a lot for your recommendations. > > Pierre > > > -- > 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]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > > >--
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.
