Re: TCP behaviour change between 2.0.36 and 2.2pre4

Philip Blundell (philb@gnu.org)
Thu, 07 Jan 1999 23:46:38 +0100


>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.

Once the other end has closed for sending you know there can be no more data
and the kernel will tell you about it when you next call read(). TCP treats
the two directions independently.

p.

-
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/