lkml.org 
[lkml]   [1999]   [Jan]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: TCP behaviour change between 2.0.36 and 2.2pre4
Date
From
>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/

\
 
 \ /
  Last update: 2005-03-22 13:49    [W:0.047 / U:0.620 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site