Is it because it requires the responses to be made to client in the order of request that causes the head of line blocking problem in HTTP 1.1?
If each request take
I think to elaborate, both offer similar performance improvements.
However pipelining (or double buffering) is hampered by buggy proxies and sometimes buggy servers. So browsers stopped supporting it.
The solution is to use a completely new protocol HTTP/2. This has a few extra features, such as out of order return, header compression and server push, but it is unclear how much improvement they provide. The key issue is the bugs.