From: Doug McIlroy <doug@cs.dartmouth.edu>
To: tuhs@tuhs.org
Subject: Re: [TUHS] v3 pipes
Date: Fri, 24 Apr 2020 08:54:39 -0400 [thread overview]
Message-ID: <202004241254.03OCsd9m066621@tahoe.cs.Dartmouth.EDU> (raw)
> why the single fd approach was abandoned? To its credit, it appears to allow for limited 2-way communication.
My understanding is that the single file descriptor broke the open-file
model, which had a single read/write pointer. Two-way communication via
Doug
next reply other threads:[~2020-04-24 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 12:54 Doug McIlroy [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-04-25 11:14 Paul Ruizendaal
2020-04-25 17:54 ` Paul Winalski
2020-04-23 13:48 [TUHS] V3 pipes Paul Ruizendaal
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=202004241254.03OCsd9m066621@tahoe.cs.Dartmouth.EDU \
--to=doug@cs.dartmouth.edu \
--cc=tuhs@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).