Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!KA9Q.BELLCORE.COM!karn
From: karn@KA9Q.BELLCORE.COM.UUCP
Newsgroups: mod.protocols.tcp-ip
Subject: TCP closes
Message-ID: <8702180554.AA04716@ka9q.bellcore.com>
Date: Wed, 18-Feb-87 00:54:14 EST
Article-I.D.: ka9q.8702180554.AA04716
Posted: Wed Feb 18 00:54:14 1987
Date-Received: Wed, 18-Feb-87 22:47:28 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 11
Approved: tcp-ip@sri-nic.arpa

Who says you have to throw away pending data when the TCP connection enters
the CLOSED state? In my implementation I put incoming data on a receive
queue and notify the user with an upcall. The user is entirely within his
rights if he chooses not to read it right away.

When the connection changes state (e.g., from TIME_WAIT to CLOSED) the user
is also notified with an upcall.  However, the control block goes away only
in response to an explicit call from the user.  This gives it a chance to
read any unread data or to throw it away.

Phil