From: jim@hosaka.SmallWorks.COM (Jim Thompson)
To: gnu-win32@cygnus.com
Cc: DKhosla@Compaq.com, colin@bird.fu.is.saga-u.ac.jp,
jes@hosaka.SmallWorks.COM, pacoid@fringeware.com,
pj@hosaka.SmallWorks.COM
Subject: Re: corruption in socket layer?]
Date: Fri, 10 Oct 1997 15:04:00 -0000 [thread overview]
Message-ID: <199710101617.LAA02323@beavis.smallworks.com> (raw)
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".
next reply other threads:[~1997-10-10 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-10 15:04 Jim Thompson [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-09 15:19 corruption in socket layer? Colin Peters
1997-10-07 12:32 Khosla, Deepak
1997-10-07 0:07 Sergey Okhapkin
1997-10-07 12:32 ` Tim Newsham
1997-10-06 14:47 Tim Newsham
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199710101617.LAA02323@beavis.smallworks.com \
--to=jim@hosaka.smallworks.com \
--cc=DKhosla@Compaq.com \
--cc=colin@bird.fu.is.saga-u.ac.jp \
--cc=gnu-win32@cygnus.com \
--cc=jes@hosaka.SmallWorks.COM \
--cc=pacoid@fringeware.com \
--cc=pj@hosaka.SmallWorks.COM \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).