From: Bakul Shah <bakul+plan9@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] channels across machines
Date: Sat, 18 Jul 2009 14:02:36 -0700 [thread overview]
Message-ID: <20090718210237.41EA95B18@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Sat, 18 Jul 2009 10:20:11 PDT." <d6f5ba377904043a4a3d5fdae198ff29@9netics.com>
On Sat, 18 Jul 2009 10:20:11 PDT Skip Tavakkolian <9nut@9netics.com> wrote:
> > Or is there a better idea? This certainly seems preferable
> > to RPC or plain byte pipes for communicating structured
> > values.
>
> i have some incomplete ideas that are tangentially related to this --
> more for handling interfaces.
>
> it seems one could write a compiler that translates an interface
> definition (e.g. IDL) into a server and a client library; 9p(2) and
> ioproc(2) can be readily used in the generated code to do the tricky
> stuff. the main part then becomes how to translate the calls across.
I did something like this (map a file of ascii struct defns
to C++ classes that included serialization/deserialization)
for the only company both of us have worked in!
These days I am likely to just use s-exprs if the choice is mine.
The joy of sexpr :-)
On Sat, 18 Jul 2009 14:32:30 CDT Eric Van Hensbergen <ericvh@gmail.com> wrote:
> getting a pipe end to something somehow is why you really want to
> leverage the namespace as a 9p file system.
Indeed but it is a separable concern (just like authentication).
next prev parent reply other threads:[~2009-07-18 21:02 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
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 [this message]
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=20090718210237.41EA95B18@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).