mauro7x / tp2_intro_distri Goto Github PK

If the last ack is lost, the other endpoint will loop for ever waiting for it.

For example:

1. Client requests the list.
2. Server sends the list, chunk by chunk.
3. The last chunk of the list (that is, the last package the client needs) arrives to the client.
4. The client sends the last ACK to the server, and then finishes the program.
5. If this last ack gets lost, the server will wait for ever.

Idea: beacuse it only can happen at the very last message of each communication, then we could implement some logic that if the ack corresponds to the last message, after some N number of timeouts, it will assume it has been received (because otherwise the other endpoint would have requested the data again).