Messages in this thread | | | Date | Wed, 6 Jan 1999 17:24:29 +0200 | From | Meelis Roos <> | Subject | Re: TCP behaviour change between 2.0.36 and 2.2pre4 |
| |
DSM> Your application needs to be fixed, it should sink all read data DSM> remaining on the socket before closing. If data is unread, TCP does DSM> not know if this was intentional and assumes that data integrity has DSM> been lost (because transfered bytes did not make it to the receiving DSM> application), and thus the RST response to indicate this.
If I understand correctly this approach has a race condition. The application can't guarantee that there's no data left: it reads all then some data arrives and then the app closes the socket.
-- Meelis Roos (mroos@tartu.cyber.ee)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |