From: Steve Kotsopoulos steve@ecf.toronto.edu
Subject: process communication ?
Date: Wed, 27 Mar 1996 12:28:01 -0500 [thread overview]
Message-ID: <19960327172801.MwaEMufAlQ6zVDcuZyXLDnzUrh5wF4MycJjCouJRTbg@z> (raw)
on a single machine, you should try using the alef communication primitives
on several machines, I'd expect IL to out-perform TCP
next reply other threads:[~1996-03-27 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-03-27 17:28 Steve [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-03-27 7:50 Gunther
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=19960327172801.MwaEMufAlQ6zVDcuZyXLDnzUrh5wF4MycJjCouJRTbg@z \
--to=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).