I've already looked at a lot of resources explaining TCP sequence numbers and ack sequence number, but they all assume(under normal circumstances) you just ack once per received payload, with the ack seq num incremented by the exact payload length received.
Let's say we last received and acked seq 500, and now we receive 100 more payload bytes. Is it technically valid TCP if instead of acking 600, we ack 100 times: starting with 501, 502, 503, ... 599, 600?
This is for an extremely latency sensitive application.
Is this idea to warm the socket by sending acks for 1 byte at a time a viable idea, or completely nonsensical and get me disconnected?
No comments:
Post a Comment