|
|
|
|
|
|
by adev_
1418 days ago
|
|
|
> How so? It is not solved on the network level (due to its use of TCP), but it is solved on application layer: slow response to one request is not blocking other requests. Like you said, it does not solve the network level: - in HTTP/2, A packet drop will slow down every HTTP transaction. - In HTTP/1 with a session pool (The usual web browser way of doing thing), it will slow down only one over X (X, size of the pool). This has been found to be a big problem over (unreliable) mobile network and that makes HTTP/2 sometimes even worst than HTTP/1. http://nl.cs.montana.edu/lab/publications/Goel_H2_extended.p... |
|
|