Live data from Hacker News

A Breakdown of HTTP Clients in Elixir

andrealeopardi.com

11–20 of 27 posts

Re: A Breakdown of HTTP Clients in Elixir

#11
post #5

This is a wonderful summary but I'm struck with how these things all seem unnecessarily complicated compared to Python' requests, Apache Commons clients, curl based libraries... I get that a lot of magic also comes from the Erlang resilience, and maybe the functional composing is certainly interesting, but JavaScripts and Clojure and arguably you could do this with anything with promises... Anyway. This sounds great…

I realized that I needed to know way more about HTTP than I wanted to when trying to write a bunch of API wrappers for crypto exchanges. There’s just… a lot of failure modes and the application needs to respond differently to each. Some failures just need a quick retry while others must be pushed all the way back to a client to decide what to do.

Re: A Breakdown of HTTP Clients in Elixir

#14
I've used HTTPoison, Tesla and more recently Req for a thin Firebase client.

I guess they all work.

I remember at some point HTTPoison & hackney were finicky with SSL certificate validation. But AFAIK HTTPoison is the only one that can do async requests to process chunks? [0]

[0] https://www.poeticoding.com/download-large-files-with-httpoi...

Re: A Breakdown of HTTP Clients in Elixir

#20

I've used HTTPoison, Tesla and more recently Req for a thin Firebase client. I guess they all work. I remember at some point HTTPoison & hackney were finicky with SSL certificate validation. But AFAIK HTTPoison is the only one that can do async requests to process chunks? [0] [0] https://www.poeticoding.com/download-large-files-with-httpoi...

See: https://gist.github.com/zachallaun/88aed2a0cef0aed6d68dcc7c1... and work underway here: https://github.com/wojtekmach/req/issues/82#issuecomment-154...
Post reply on HN