From: Mechiel Lukkien <mechiel@xs4all.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] channels across machines
Date: Sat, 18 Jul 2009 12:38:56 +0200 [thread overview]
Message-ID: <20090718103856.GG8655@knaagkever.ueber.net> (raw)
In-Reply-To: <158688033fe375ed6e935e472986d876@quanstro.net>
On Sat, Jul 18, 2009 at 06:25:19AM -0400, erik quanstrom wrote:
> i think the general idea is that if you want to do this between
> arbitrary machines, you provide a 9p interface. you can think
> of 9p as a channel with a predefined set of messages. acme
> does this. kernel devices do this.
>
> however inferno provides file2chan
> http://www.vitanuova.com/inferno/man/2/sys-file2chan.html.
> of course, somebody has to provide the 9p interface, even
> if that's just posting a fd to /srv.
>
> if you wanted to do something like file2chan in plan 9 and c, you're
> going to have to marshal your data. this means that chanconnect
> as specified is impossible.
[...]
>
> after whittling away problem cases, i think one is left with pipes,
> and it seems pretty clear how to connect things so that
> chan <-> pipe <-> chan. one could generalize to multiple
> machines by using tools like cpu(1).
inferno's file2chan is local too, just giving a simple interface to
handling plain reads & writes on a file. unless i've been using it
wrong.
what i like about file2chan is that you can return your own error
strings. as far is i know, that's not possible with pipes. if it is
possible, i'm very interested to learn how it's done.
mjl
next prev parent reply other threads:[~2009-07-18 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 7:43 Bakul Shah
2009-07-18 10:25 ` erik quanstrom
2009-07-18 10:38 ` Mechiel Lukkien [this message]
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=20090718103856.GG8655@knaagkever.ueber.net \
--to=mechiel@xs4all.nl \
--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).