From: Andrey A Mirtchovski <aam396@mail.usask.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] message passing.. sci programming
Date: Wed, 28 Mar 2001 23:30:04 -0600 [thread overview]
Message-ID: <Pine.GSO.4.10.10103282325420.27629-100000@ultra5f.usask.ca> (raw)
In-Reply-To: <200103290431.VAA06869@fred.acl.lanl.gov>
I was looking at the 9p protocol for implementing some sort of message
passing in my project.. i had to abandon it for lack of time though...
depending on how close one keeps to the 'all is file' paradigm 9p could
really save the day :)
andrey
On Wed, 28 Mar 2001, Nehal N. Desai wrote:
> sorry for the elliptic (and incorrect) nature of the previous email.
> here's a corrected one..
>
next prev parent reply other threads:[~2001-03-29 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-29 4:24 Nehal N. Desai
2001-03-29 4:31 ` Nehal N. Desai
2001-03-29 5:30 ` Andrey A Mirtchovski [this message]
2001-03-29 6:14 ` Jim Choate
2001-03-29 17:05 presotto
2001-03-29 17:17 ` Ronald G Minnich
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.GSO.4.10.10103282325420.27629-100000@ultra5f.usask.ca \
--to=aam396@mail.usask.ca \
--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).