In this guide
Recovery preserves bytes but uses timeA TCP segment is not a media segmentUse connection evidence carefullyTCP provides applications with a reliable, ordered byte stream. It detects missing or erroneous transport data and uses recovery mechanisms including retransmission. Many HTTP media transfers operate over TCP-based connections.
Reliability describes the delivered byte stream, not a guarantee that every media deadline will be met. Data can arrive correctly after recovery while the player has already spent its available buffer.
Recovery preserves bytes but uses time
If an earlier portion of a TCP stream is missing, later bytes cannot simply be presented to the application as though the gap were absent. Recovery can add delay and affect the achieved transfer rate. This differs from an application receiving arbitrary corrupted video bytes and being expected to conceal every missing network packet itself.
An original hypothetical segment needs one missing transport portion retransmitted. The completed media resource can still be correct, but its request may take longer than neighboring segments. Whether the viewer sees a pause depends on deadlines and playable buffer already available.
A TCP segment is not a media segment
Transport segmentation divides network delivery into units defined by TCP. An HLS media segment is an application resource covering a span of media time. One media segment normally involves many transport packets; the terms should not be used interchangeably in a report.
| Term | Layer |
|---|---|
| TCP segment | Transport delivery unit |
| HLS media segment | Media resource/timeline unit |
| TCP retransmission | Recovery of transport data |
| HTTP error response | Application-layer outcome |
| Buffer underrun | Playback lacks needed media in time |
Use connection evidence carefully
A retransmission counter is useful only with its connection and interval. Cumulative system-wide values can include unrelated traffic. A retry visible in the media application is not necessarily a TCP retransmission; the app may have started a new HTTP request after an error.
Correlate transport recovery with actual request timing and buffer behavior before assigning a playback effect. A documented TCP mechanism does not establish where a loss occurred or promise that changing the transport will improve every stream.