HTTP/2.0 becomes increasingly more widespread and fasthttp looks more and more abandoned. AFAIK nothing from this list was implemented and it's been a year, since it was last updated. Issues left unanswered and PR's are not being merged or reviewed.
To address all of those points I plan to add net/http clients: one with a forced HTTP/1.1 and another one with HTTP/2.0 enabled.
Client will be switched by setting a flag, probably, something like --fasthttp, --http1, --http2. By default fasthttp client will be used.
HTTP/2.0 becomes increasingly more widespread and fasthttp looks more and more abandoned. AFAIK nothing from this list was implemented and it's been a year, since it was last updated. Issues left unanswered and PR's are not being merged or reviewed.
To address all of those points I plan to add
net/httpclients: one with a forced HTTP/1.1 and another one with HTTP/2.0 enabled.Client will be switched by setting a flag, probably, something like
--fasthttp,--http1,--http2. By defaultfasthttpclient will be used.