>"In HTTP/2, the single connection carries hundreds of streams. In this case, when we lose one packet, "one hundred streams are waiting for that one single packet"
Could someone elaborate on how this is worse if all of those streams are part of the some client request? Am I missing something really obvious.
>"In HTTP/2, the single connection carries hundreds of streams. In this case, when we lose one packet, "one hundred streams are waiting for that one single packet"
Could someone elaborate on how this is worse if all of those streams are part of the some client request? Am I missing something really obvious.