[erlang-questions] better HTTP client?

[Dmitry Kolesnikov]

Hello Chris,

I am afraid that your requirements goes beyond http client spec. You are looking for pool of http client workers accomplished with async queue in front.

I do not think that you will find a client http library that fulfills it. I would integrate queue, pool and light http client by myself. It would take more time but you will be sure about your needs.


Best Regards,
Dmitry >-|-|-*>


On 9.9.2013, at 1.58, "Chris King" <colanderman@REDACTED> wrote:

> Hi all,
> 
> Due to various architectural bugs in the inets:httpc module (which I have reported) related to queueing multiple requests to a single server, I'm looking for a replacement for my application.
> 
> The use case requires queuing many GET requests to a small number of servers; taking advantage of keep-alive/pipelining when available; and allowing outstanding unserviced requests to be canceled.  I don't care about streaming or writing to disk or any sort of upload capability.  Any suggestions or should I roll my own?
> 
> (The work required to re-architect inets:httpc compared to writing a simple server that meets exactly my needs is too much for me right now.)
> 
> Thanks,
> Chris
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions