Updated http client from net/http to fasthttp

[code-xD]

Description

Modified Aptos Http client from net/http to fasthttp. There has been issues with connection issues with newer Aptos blockchain like Movement.

Test Plan

Related Links

[gregnazario]

This looks generally good, but my main concern is that it doesn't support HTTP/2?

[code-xD]

This looks generally good, but my main concern is that it doesn't support HTTP/2?

Hey @gregnazario,
I will have to check the compatibility of the new http package with HTTP/2. Do you have any sample RPC Endpoints which I can use to test this behaviour?

[gregnazario]

This looks generally good, but my main concern is that it doesn't support HTTP/2?

Hey @gregnazario,

I will have to check the compatibility of the new http package with HTTP/2. Do you have any sample RPC Endpoints which I can use to test this behaviour?

All of the Aptos labs endpoints built in by default support HTTP/2 as far as I know, which by itself should give more performance boost than the handling on the client side afaik.

I found when I set the client pool configuration correctly, I got good concurrency and performance out of it

[code-xD]

This looks generally good, but my main concern is that it doesn't support HTTP/2?

Hey @gregnazario,

I will have to check the compatibility of the new http package with HTTP/2. Do you have any sample RPC Endpoints which I can use to test this behaviour?

All of the Aptos labs endpoints built in by default support HTTP/2 as far as I know, which by itself should give more performance boost than the handling on the client side afaik.

I found when I set the client pool configuration correctly, I got good concurrency and performance out of it

Yeah, the connection pool management for this library is far better and it's architected in a manner wherein user have the control over when they want to release the request and response body thereby mitigating memory leaks.