From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] channels across machines
Date: Sat, 18 Jul 2009 00:43:38 -0700 [thread overview]
Message-ID: <20090718074338.1A91D5B18@mail.bitblocks.com> (raw)
Has anyone extended the idea of channels where the
sender/receiver are on different machines (or at least in
different processes)? A netcat equivalent for channels!
Actual plumbing seems easy: one can add a `proxy' thread in
each process to send a message via whatever inter process
mechanism is available. One issue would be for the two sides
to identify a specific channel. I imagine something like the
following would work.
// on the client:
chan = chanconnect("<host>:<port>", elemsize, nelem);
// on the server:
x = chanbind("<port>", elemsize, nelem);
chan = chanaccept(x); // to allow multiple connections
Or one can build this on top of a socket or file descriptor.
Another issue is endianness (unless all processors are the
same type). Yet another issue is sending variable size
things. In a single address space you can pass a pointer +
may be a size but that trick doesn't work across process (or
machine boundaries) -- so pretty much have to add some
marshalling/unmarshalling that knows about types.
Or is there a better idea? This certainly seems preferable
to RPC or plain byte pipes for communicating structured
values.
Thanks!
--bakul
next reply other threads:[~2009-07-18 7:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 7:43 Bakul Shah [this message]
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
2009-07-18 8:38 Akshat Kumar
2009-07-18 16:53 ` J.R. Mauro
2009-07-18 17:06 ` erik quanstrom
2009-07-24 10:23 ` maht
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=20090718074338.1A91D5B18@mail.bitblocks.com \
--to=bakul+plan9@bitblocks.com \
--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).