3 ms·
Even if the delayed packet does eventually arrive without needing to be resent, it still has the effect of holding up all the other streams. Only if you're mul
by Animats 4y ago
Even if the delayed packet does eventually arrive without needing to be resent, it still has the effect of holding up all the other streams.
Only if you're multiplexing multiple streams inside one TCP connection. Multiple TCP connections will not affect each other.
- quietbritishjim 4y agoYes, that is exactly what HTTP allows: multiple data streams over a single TCP connection. In general, that's a good thing: if you have a page with dozens of small files (icon images, CSS, JS fragments, etc.) then you don't want to instantiate a new TCP connection for every one. Browsers typically have multiple HTTP connections open as a compromise so that you don't need a new TCP connection for every file but don't have the head of line problem so severely. But it's not as good as fixing the underlying problem.