 | 1 | initial version |
I am new to TCP traffic analyze so I will just put my understanding here, might not be correct.
Yes it will slow down the sending throughput. Server send Dup Ack to Client, Client will think the packet is lost, therefor reduce congestion window ( not server side receiving window), and throughput will be reduced as well.
Server should keep the received data in the buffer, the client won't send data more than the buffer size ( it will see client window full). The data will not be sent to application until the missing packet is resent by the client. When TCP data is delivered to application, it's always in order.
| | 2 | No.2 Revision |
I am new to TCP traffic analyze so I will just put my understanding here, might not be correct.
Yes it will slow down the sending throughput. Server send Dup Ack to Client, Client will think the packet is lost, therefor reduce congestion window ( not server side receiving window), and throughput will be reduced as well.
Server should keep the received data in the buffer, the client won't send data more than the buffer size ( it will see client server receiving window full). The data will not be sent to application until the missing packet is resent by the client. When TCP data is delivered to application, it's always in order.
| | 3 | No.3 Revision |
I am new to TCP traffic analyze so I will just put my understanding here, might not be correct.
Yes it will slow down the sending throughput. Server send Dup Ack to Client, Client will think the packet is lost, therefor reduce congestion window ( not server side receiving window), and throughput will be reduced as well.
Server should keep the received data in the buffer, the client won't send data more than the buffer size ( it will see server receiving window full). The data will not be sent to application until the missing packet is resent by the client. received. When TCP data is delivered to application, it's always in order.
