From: Derek Fawcus <dfawcus+lists-tuhs@employees.org>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] sockets (was Re: First appearance of named pipes)
Date: Sun, 8 Mar 2020 16:13:32 +0100 [thread overview]
Message-ID: <20200308151332.GA70333@clarinet.employees.org> (raw)
In-Reply-To: <CAKzdPgyQE6idAQNJ4sarjOUL8nvAF7m9BgY6NCjep6_wZMpjzQ@mail.gmail.com>
On Sun, Mar 08, 2020 at 01:36:14PM +1100, Rob Pike wrote:
> Always bemused me that to get a named local I/O connection one ended
> up with "Unix domain (what does that even mean?) sockets" rather than
> named pipes,
Yeah - I always found that a bit weird, having to use socketpair()
to get a bidirectional "pipe".
> I've been told, but haven't confirmed, that
> early sockets didn't even support read and write. They still don't
> support open and close, and never will.
Err - granted on the open; but if my memory serves, close() has been
supported on them ever since I started using them ('87). Otherwise
the normal fork/dup/close/exec pattern for child processes would not
work.
Now what would have been useful is a way to have distinct fd's for
the local read and write end of (e.g.) a TCP socket - such that one
direction could be closed w/o closing the other. Or maybe some
fcntl() to dup the bidirectional fd in to a pair of unidirectional
fds. That way one could dispense with shutdown for closing one
direction, making children and fd passed programs socket agnostic.
DF
next prev parent reply other threads:[~2020-03-08 15:14 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 22:44 [TUHS] First appearance of named pipes Noel Chiappa
2020-03-07 12:17 ` Paul Ruizendaal
2020-03-07 13:29 ` Clem Cole
2020-03-07 16:39 ` Derek Fawcus
2020-03-08 2:36 ` Rob Pike
2020-03-08 2:47 ` Larry McVoy
2020-03-08 13:07 ` Ralph Corderoy
2020-03-08 13:25 ` arnold
2020-03-08 3:06 ` Dave Horsfall
2020-03-08 7:16 ` arnold
2020-03-08 15:13 ` Derek Fawcus [this message]
2020-03-09 23:22 ` [TUHS] sockets (was Re: First appearance of named pipes) Grant Taylor via TUHS
2020-03-09 23:44 ` Larry McVoy
2020-03-23 8:49 ` Peter Pentchev
2020-03-24 9:47 ` Derek Fawcus
2020-03-25 23:25 ` Grant Taylor via TUHS
2020-03-25 23:47 ` Richard Salz
2020-03-26 0:11 ` Grant Taylor via TUHS
2020-03-26 0:18 ` Richard Salz
2020-03-26 1:08 ` Grant Taylor via TUHS
2020-03-26 2:38 ` Dave Horsfall
2020-03-26 3:08 ` Rob Pike
2020-03-26 3:43 ` George Michaelson
2020-03-26 4:11 ` Grant Taylor via TUHS
2020-03-28 11:12 ` Peter Pentchev
2020-03-28 11:14 ` Peter Pentchev
2020-03-28 16:03 ` Steffen Nurpmeso
2020-03-26 1:20 ` Tony Finch
2020-03-27 10:51 ` Derek Fawcus
2020-03-09 23:22 ` [TUHS] First appearance of named pipes Grant Taylor via TUHS
2020-03-10 7:29 ` arnold
2020-03-11 2:47 ` Grant Taylor via TUHS
2020-03-11 7:02 ` arnold
2020-03-10 13:49 ` Chet Ramey
2020-03-10 20:26 ` Dave Horsfall
2020-03-10 20:37 ` Chet Ramey
2020-03-11 2:51 ` Grant Taylor via TUHS
2020-03-08 23:09 [TUHS] sockets (was Re: First appearance of named pipes) Norman Wilson
2020-03-09 17:09 ` Tony Finch
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=20200308151332.GA70333@clarinet.employees.org \
--to=dfawcus+lists-tuhs@employees.org \
--cc=tuhs@minnie.tuhs.org \
/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).