No, but it clearly state the flaw of HTTP2.0: a broken by design replacement of all possible TCP/IP layers on top of a subtly broken in some places stack.
Would you trust this unstable "pragmatic" house of card to deliver its promises of being "working"?
Comments
No, but it clearly state the flaw of HTTP2.0: a broken by design replacement of all possible TCP/IP layers on top of a subtly broken in some places stack.
Would you trust this unstable "pragmatic" house of card to deliver its promises of being "working"?