Darío

Hello. I know it's been long but just wanted to tell you all that I have a working on HTTP/2 a little. Example [here](https://github.com/dgrr/http2/blob/master/examples/simple/main.go). Why after 2 years I recovered...

For now I am a bit busy. I'll continue working in a few weeks. The client is my priority number one. I'll do the server later.

@renanbastos93 you can pick the issue you want and start a discussion/solving the issue

Try to allocate only the needed resources. In this case try to call *Release functions. And do not make a new client every time you call `doRequest`, try to parse...

So @marcoroganovic which examples do you need?

The client automatically handles your connections with the servers. So if you open a connection with a host and you want to send more than one request this won't create...

Well... I don't know so much about resources, just keep your eye on HTTP-related projects like https://github.com/valyala/tcplisten

@9mm No, I said it keeps the connection open until one of the peers closes the connection. And I am not referring to anything related to HTTP/2. HTTP/1.1 supports request...

I don't see why fasthttp needs a wiki. It's pretty straightforward to use.

@aiddroid Using the Request structure :) Just like this ```go package main import ( "log" "github.com/valyala/fasthttp" ) func main() { req := fasthttp.AcquireRequest() res := fasthttp.AcquireResponse() defer fasthttp.ReleaseRequest(req) defer fasthttp.ReleaseResponse(res)...