This is the mail archive of the
cygwin@sourceware.cygnus.com
mailing list for the Cygwin project.
Re: corruption in socket layer?]
- To: gnu-win32 at cygnus dot com
- Subject: Re: corruption in socket layer?]
- From: jim at hosaka dot SmallWorks dot COM (Jim Thompson)
- Date: Fri, 10 Oct 1997 11:17:46 -0500
- Cc: DKhosla at Compaq dot com, colin at bird dot fu dot is dot saga-u dot ac dot jp, jes at hosaka dot SmallWorks dot COM, pacoid at fringeware dot com, pj at hosaka dot SmallWorks dot COM
Colin (and Microsoft) should read RFC793:
CLOSE is an operation meaning "I have no more data to send." The
notion of closing a full-duplex connection is subject to ambiguous
interpretation, of course, since it may not be obvious how to treat
the receiving side of the connection. We have chosen to treat CLOSE
in a simplex fashion. The user who CLOSEs may continue to RECEIVE
until he is told that the other side has CLOSED also. Thus, a program
could initiate several SENDs followed by a CLOSE, and then continue to
RECEIVE until signaled that a RECEIVE failed because the other side
has CLOSED. We assume that the TCP will signal a user, even if no
RECEIVEs are outstanding, that the other side has closed, so the user
can terminate his side gracefully. A TCP will reliably deliver all
buffers SENT before the connection was CLOSED so a user who expects no
data in return need only wait to hear the connection was CLOSED
successfully to know that all his data was received at the destination
TCP. Users must keep reading connections they close for sending until
the TCP says no more data.
The second to last sentence makes the behavior of a conformant TCP clear.
Jim
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".