Kirill Danshin

hmm. I think I know how to fix it. pending analysis.

Changing existing tests may hint that we might've broken backward compatibility. I doubt it's a good idea to change old public api behavior too much

@dgrr awesome! thanks for your work. is there any roadmap and current status? when you finish your work, we can embed it in the fasthttp and finally support http/2 officially....

@dgrr I think we should at least try and benchmark embedded version and see if we can get any better solution for this

@dgrr huge shout-out to you for that work 👍

@avkhra do you have the same results if you put net/http and fasthttp servers in different binaries?

fasthttp is used by at least one of the largest media corporations in the world. They use it for some critical services. it's frequently being used in RTB platforms, HFT...

hey @gitmko0 here's the first snippet, translated for fasthttp, and a variant without middlewares ```go func HystrixHandler(h func(*fasthttp.RequestCtx), command string) func(*fasthttp.RequestCtx) { return func(ctx *fasthttp.RequestCtx) { hystrix.Do(command, func() error {...

@panjf2000 actually, we already have an outline for the migration, and I’m going to ask for some help and additional monitoring @ github support, so we could fix any problems...

@erikdubbelboer I'll test it, if you don't mind @tsingson we plan to move the development to github.com/fasthttp/fasthttp, but keep updating this repo to allow some time for migration