From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: 9fans@9fans.net
Subject: [9fans] channels across machines
Date: Sat, 18 Jul 2009 04:38:07 -0400 [thread overview]
Message-ID: <4e6ca2050907180138n10d83337v193e031bb56192b3@mail.gmail.com> (raw)
The idea seems inviting at first, but have you
given a thought to using plumber(4) for
"interprocess messaging" (which is what you
want, from what I understand)? This seems
more appropriate for communication amongst
processes alien to one another than something
so code-level like a chan extension.
at least, in terms of Plan 9
ak
next reply other threads:[~2009-07-18 8:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 8:38 Akshat Kumar [this message]
2009-07-18 16:53 ` J.R. Mauro
2009-07-18 17:06 ` erik quanstrom
2009-07-24 10:23 ` maht
-- strict thread matches above, loose matches on Subject: below --
2009-07-18 7:43 Bakul Shah
2009-07-18 10:25 ` erik quanstrom
2009-07-18 10:38 ` Mechiel Lukkien
2009-07-18 11:33 ` erik quanstrom
2009-07-18 18:52 ` Bakul Shah
2009-07-18 19:32 ` Eric Van Hensbergen
2009-07-18 17:20 ` Skip Tavakkolian
2009-07-18 17:22 ` J.R. Mauro
2009-07-18 21:02 ` Bakul Shah
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=4e6ca2050907180138n10d83337v193e031bb56192b3@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--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).