You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You really shouldn't be using Net/HTTP for production applications.
Here are many reasons why you should not use Net/HTTP:
single-threaded
poor connection design
opt-in to keep-alive
poor SSL support
does not support cookies
cannot follow redirects
It is one of the slowest HTTP clients for Ruby
I would recommend using one of the libcurl libraries, or one of the "original" ones (not built on top of Net/HTTP like most of the clients), such as curb, em-http-request, or the oldest and my personal favorite, httpclient.
@tkdberger Not right now. I haven't had much time to work on this recently and this is a low-priority change for me since the app is working at the moment.
You really shouldn't be using Net/HTTP for production applications.
Here are many reasons why you should not use Net/HTTP:
I would recommend using one of the libcurl libraries, or one of the "original" ones (not built on top of Net/HTTP like most of the clients), such as curb, em-http-request, or the oldest and my personal favorite, httpclient.
Here's a nice slideshare to provide some statistical information regarding Ruby HTTP clients, made by Hiroshi Nakamura, Ruby developer and developer of HTTPClient: http://www.slideshare.net/HiroshiNakamura/rubyhttp-clients-comparison
The text was updated successfully, but these errors were encountered: