[ann] hackney 1.17.0

[Benoit Chesneau]

I think it coil have been a complete replacement since a long time ago :)

About your questions:

1. In current community version, you get directly the socket from the pool,
so it depends if the pool is overloaded or not but that should be fast. In
a coming version reusing a socket is local so it doesn't go back and forth.
2. Yes. This is actually how is handled socks5 or the proxy.

Feel free to ping me in private if you want more info

Benoît


On Sun, Dec 20, 2020 at 10:29 AM Max Lapshin <max.lapshin@REDACTED> wrote:

> Wow, so with pool management it is a complete replacement for lhttpc?
>
>
> Short question: I have several specific hacks to lhttpc:
>
> 1. very detailed timing response: how much time were waiting for
> socket, for connecting, for first byte, for headers, etc.
> 2. our own internal socket source. It is a normal Socket, but we have
> some communication before HTTP.  Is it possible to provide some kind
> of transport module to hackney?
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20201229/5cfcee3c/attachment.htm>