From: Ronald G Minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] message passing.. sci programming
Date: Thu, 29 Mar 2001 10:17:36 -0700 [thread overview]
Message-ID: <Pine.LNX.4.20.0103291016470.25491-100000@snaresland.acl.lanl.gov> (raw)
In-Reply-To: <20010329170600.1C441199EB@mail.cse.psu.edu>
On Thu, 29 Mar 2001 presotto@plan9.bell-labs.com wrote:
> What semanitcs are you looking for with the messages? If it's
> just n to 1 with in order delivery and message boundaries, you
> can just use pipes bound into the file system. The reader does
> the bind and then exports (via exportfs) his name space to every
> system that wants to send him messages. Each party can do the same
> to affect 2 way communication. No special tools necessary.
I've been wondering about this. Does anyone know how much you lose in
bandwidth over raw IL or TCP links?
ron
next prev parent reply other threads:[~2001-03-29 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 17:05 presotto
2001-03-29 17:17 ` Ronald G Minnich [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-29 4:24 Nehal N. Desai
2001-03-29 4:31 ` Nehal N. Desai
2001-03-29 5:30 ` Andrey A Mirtchovski
2001-03-29 6:14 ` Jim Choate
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=Pine.LNX.4.20.0103291016470.25491-100000@snaresland.acl.lanl.gov \
--to=rminnich@lanl.gov \
--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).