[erlang-questions] What lib to use for http requests
Sun Dec 14 22:44:23 CET 2014
Your questions are excellent ones. I agree with your assertion that it'd
be nice if http[c,d] were well-supported and kept up to date in the
standard library, but on the other hand that's equivalent to me saying that
it would be nice if other people did some tedious work. The OTP team
appears to be, ah, not luxuriously staffed, and, er, somewhat
well-task-committed towards commercial customers, so it's easy to see how
they're not spending their days fastidiously refactoring the standard
It would be interesting to know what the OTP team's official position on
accepting new libraries and deprecating old ones is, and what the process
would look like (EEP? Other?).
On Sat, Dec 13, 2014 at 12:27 PM, Tuncer Ayaz <tuncer.ayaz@REDACTED> wrote:
> On Fri, Dec 12, 2014 at 9:03 PM, Felix Gallo wrote:
> > httpc has some weird bugs under load and should be retired from the
> > standard distribution.
> Hi Felix,
> you clearly have experienced httpc's limitations/bugs, so I'm curious
> to hear your thoughts on the following.
> What's the solution?
> 1) replace httpc's implementation with hackney?
> 2) rewrite httpc?
> 3) drop httpc?
> I haven't used httpc enough to run into the mentioned issues, but I do
> wonder why instead of fixing httpc we, as a community, write more than
> a few alternative http clients. Is it because it's easy to do like a
> I think it's very important that the network code in otp.git is fixed
> and improved where necessary to leave external httpd or httpc libs to
> special purpose cases. Other languages don't seem to suffer from this
> and carry http[c,d] libs which are well-maintained and the go to
> implementation for common use cases.
> Also see:
> With all that said, I'm confident the OTP team would more than welcome
> improvements or even replacements for inets components.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the erlang-questions