Timeline for Acknowledgement reliability using UDP
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2017 at 8:07 | comment | added | Stack Exchange Broke The Law | @Angew done now. | |
| Jun 16, 2017 at 8:06 | history | edited | Stack Exchange Broke The Law | CC BY-SA 3.0 | added 199 characters in body |
| Jun 16, 2017 at 7:51 | comment | added | Angew is no longer proud of SO | Regarding the thing in parenthesis (sending ACK for packets you already got), I think you should actually emphasise it instead of parenthesising it. It seems to be missing from the OP's understanding (or at least its description). | |
| Jun 15, 2017 at 21:25 | comment | added | Stack Exchange Broke The Law | @supercat I wouldn't say that's essential; more like an optimization. | |
| Jun 15, 2017 at 19:09 | comment | added | supercat | An essential feature of TCP is that the sender doesn't need to care about whether any particular packet got acknowledged, but mostly needs to care about the "high water mark" and how long packets have been outstanding without the high-water mark moving. | |
| Jun 15, 2017 at 11:20 | history | answered | Stack Exchange Broke The Law | CC BY-SA 3.0 |