inet
inet copied to clipboard
TCP "read" syscall missing, receive buffer never fills up
The TCP model doesn't implement a "read" syscall, i.e. data that have been received (in the correct order) are passed up immediately to the application layer.
Therefore one cannot model a situation when the app doesn't read the received data from the buffer, it fills up, and TCP must report closed window to the sender.
inet version: 2.99.0