From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: Charles Forsyth Date: Sat, 4 Feb 2017 09:58:39 +0000 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a1145b474591c270547b17136 Subject: Re: [9fans] adding TCP half-duplex close Topicbox-Message-UUID: b3525248-ead9-11e9-9d60-3106f5b1d025 --001a1145b474591c270547b17136 Content-Type: text/plain; charset=UTF-8 On 4 February 2017 at 01:56, Skip Tavakkolian wrote: > Shutting down the write-end (i.e. 'shut_wr'), should send FIN, and > transition to Finwait1. i'd make it a "read" or "write" parameter to the existing "hangup" message. older implementations that don't accept the parameter will give an error on the request because the current tcp.c doesn't accept a parameter --001a1145b474591c270547b17136 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 4 February 2017 at 01:56, Skip Tavakkolian <skip.tavakkolian@g= mail.com> wrote:
Shutting= down the write-end (i.e. 'shut_wr'), should send FIN, and transiti= on to Finwait1.

i'd make it a "read" or= "write" parameter to the existing "hangup" message. ol= der implementations that don't accept the parameter will give an error = on the request because the current tcp.c doesn't accept a parameter
--001a1145b474591c270547b17136--