Ask Your Question

Revision history [back]

The whole point of TCP's sequence mechanism is to ensure that the application receives a stream of data in the correct order, regardless of what has gone wrong in the transmission of the TCP segments.

As long as the receiving TCP stack can reassemble the segments within it's constraints of buffer memory capacity and timeouts and retries, then the data will eventually be delivered to the application, which is none the wiser, apart from maybe thinking the data is a bit slow to come in which, may in turn, affect the application performance.

Examining the traffic with Wireshark with the sequence analysis enabled shows the true picture though and may or may not need some network fault finding to reduce the issue to an acceptable level.