Why not apply this to net/http? about fasthttp HOT 6 CLOSED

FYI, I tried optimizing net/http before starting fasthttp. About 50% of memory allocations per request were shaved, but this didn't give significant performance gain. So I gave up and started fasthttp :)

from fasthttp.

👍 👍

from fasthttp.

Along the same lines, why does this not adhere to the same interface is net/http? Perhaps I misread the documentation, but at least ListenAndServe has a different interface.

from fasthttp.

I agree, seemed cumbersome to have to assign handlers. I would like it to follow more or less the net/http library like this https://gist.github.com/tristanwietsma/8444cf3cb5a1ac496203

from fasthttp.

@sybrandy true, deal breaker

from fasthttp.

• net/http efficiency will never reach fasthttp due to API constraints and backwards compatibility requirements.
• fasthttp cannot have API identical to net/http due to performance reasons.

See the FAQ for more information.

from fasthttp.