9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] bidirectional pipes
Date: Thu,  2 May 2002 14:35:41 -0700	[thread overview]
Message-ID: <200205022135.g42LZfXB014631@ducky.net> (raw)
In-Reply-To: <20020502203924.12462.qmail@g.bio.cse.psu.edu>

>While this is cool, I have to admit that I never really liked
>bidirectional pipes, because if you want to close half of the connection,
>you either need something like bsd's shutdown(), or a way to recover
>your control file which hopefully will let you half-close.

I'm curious?  Why does this bother you?  Just let half the connection
go unused.

My very first reaction to bidirectional pipes, when I first heard of
them in some journal article about v8 Unix many years ago, was: wow,
that is such an obvious win, why wasn't it done years ago?

The only thing I can think to explain your position is that it's a
semi-religious issue, rather like dynamically typed vs. staticly
typed languages: some people like the greater flexibility associated
with type checks only at the point you actually try to use the
value, whereas others want to get their error messages right away.
And some people like the flexibility of bidirectional pipes, whereas
others would like to get errors back from "incorrect" read and write
system calls immediately.


  reply	other threads:[~2002-05-02 21:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02 20:39 [9fans] getting at Windows files from VMware-hosted Plan 9 Scott Schwartz
2002-05-02 21:35 ` Mike Haertel [this message]
2002-05-02 22:24   ` [9fans] bidirectional pipes Scott Schwartz
2002-05-03 10:09   ` Boyd Roberts
2002-05-04  9:14   ` Steve Kilbane
2002-05-02 21:55 Geoff Collyer
2002-05-02 22:30 Russ Cox
2002-05-03  7:19 forsyth

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=200205022135.g42LZfXB014631@ducky.net \
    --to=mike@ducky.net \
    --cc=9fans@cse.psu.edu \
    /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).