9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] parallel programming in Plan 9
Date: Thu, 19 Feb 2004 19:18:00 +0000	[thread overview]
Message-ID: <545c4c1d03136de6870aae60bf26edb3@vitanuova.com> (raw)
In-Reply-To: <01600f54e32a3088b1f96a7caec89ca3@plan9.bell-labs.com>

> However if you have to pass
> messages twixt programs, it doesn't really help deciding what
> the messages should look like or how to marshal them.

...  although i've found that using 9p helps focus the mind on to what
messages are really necessary, and the conventional textual
representation of messages lends itself well to

a) ease of explanation/documentation and
b) proper separation of interface from implementation on both ends of
the connection.

this contrasts with RPC-style marshalling where the RPC interface is
often taken directly from the procedural interface on the server,
which is not necessarily the way that the client would choose to do
things.

i guess the downside is that if you really do have a method that takes
data and in and returns data (not an error indication), you've got 4
messages rather than 2.



  reply	other threads:[~2004-02-19 19:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-18 21:17 David Presotto
2004-02-19 19:18 ` rog [this message]
2004-02-20 20:28   ` [9fans] transpose rog
  -- strict thread matches above, loose matches on Subject: below --
2004-02-18 21:02 [9fans] parallel programming in Plan 9 James Horey
2004-02-18 21:17 ` Scott Schwartz
2004-02-18 22:36   ` James Horey
2004-02-18 22:52     ` David Presotto
2004-02-18 23:23     ` Scott Schwartz
2004-02-19  5:00 ` andrey mirtchovski
2004-02-19 14:35   ` ron minnich
2004-02-19 14:40     ` boyd, rounin

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=545c4c1d03136de6870aae60bf26edb3@vitanuova.com \
    --to=rog@vitanuova.com \
    --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).