From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] adding TCP half-duplex close
Date: Sat, 4 Feb 2017 10:11:34 +0000 [thread overview]
Message-ID: <CAOw7k5jr8hPV=Ze_aJpXqFGJ=Z8KXu_e9LC1xAkf2R95uX05iw@mail.gmail.com> (raw)
In-Reply-To: <CAOw7k5gWKxu2WGXdqZqWJLsO5cwm_AzMCK1a9Q5Kjx9A_aG4KA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
I did once have a use for this in an o/s of mine, in a sort of network pipe
to servers, but it was so variably implemented by other systems (data was
flushed, or not) I gave it up as not particularly useful in practice,
except between two known systems that did what you wanted.
On 4 February 2017 at 09:58, Charles Forsyth <charles.forsyth@gmail.com>
wrote:
>
> On 4 February 2017 at 01:56, Skip Tavakkolian <skip.tavakkolian@gmail.com>
> 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
>
[-- Attachment #2: Type: text/html, Size: 1425 bytes --]
next prev parent reply other threads:[~2017-02-04 10:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 1:56 Skip Tavakkolian
2017-02-04 6:29 ` Bakul Shah
2017-02-05 4:24 ` Skip Tavakkolian
2017-02-04 9:58 ` Charles Forsyth
2017-02-04 10:11 ` Charles Forsyth [this message]
2017-02-04 10:13 ` Charles Forsyth
2017-02-05 4:39 ` Skip Tavakkolian
2017-02-05 5:23 ` Bakul Shah
2017-02-05 15:51 ` Charles Forsyth
2017-02-05 15:54 ` Charles Forsyth
2017-02-05 18:13 ` Bakul Shah
2017-02-05 21:48 ` Charles Forsyth
2017-02-10 8:49 ` Skip Tavakkolian
2017-02-12 3:28 ` Skip Tavakkolian
2017-02-05 7:54 ` Fran. J Ballesteros
2017-02-05 4:16 ` Skip Tavakkolian
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='CAOw7k5jr8hPV=Ze_aJpXqFGJ=Z8KXu_e9LC1xAkf2R95uX05iw@mail.gmail.com' \
--to=charles.forsyth@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).