From: roger peppe <rogpeppe@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Thrift RPC
Date: Thu, 13 Aug 2009 09:42:26 +0100 [thread overview]
Message-ID: <df49a7370908130142h4c82f836n96ef577c01d4d747@mail.gmail.com> (raw)
In-Reply-To: <E2DB8264-FAE5-4918-A751-8F94EED0B8A9@sun.com>
2009/8/13 Roman Shaposhnik <rvs@sun.com>:
> Am I totally missing something or hasn't been the binary RPC
> of that style been dead ever since SUNRPC? Hasn't the eulogy
> been delivered by CORBA? Haven't folks realized that S-exprs
> are really quite good for data serialization in the heterogeneous
> environments (especially when they are called JSON)
i'm not familiar with Thrift, but i've done some stuff with google protobufs,
from which i think Thrift is inspired.
speaking of protobufs, i don't think they're a bad idea.
they're specifically designed to deal
with forward- and backward-compatibility, which is something
you don't automatically get with s-expressions, and if you're
dealing with many identically-typed records, the fact that each field
in each record is not string-tagged counts saves a lot of bandwidth
(and makes them more compressible, too).
we don't use text for 9p, do we?
> and you
> really shouldn't be made to figure out how large is the integer
> on a host foo?
?
next prev parent reply other threads:[~2009-08-13 8:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 3:33 Roman Shaposhnik
2009-08-13 3:49 ` Tim Newsham
2009-08-13 4:33 ` Roman Shaposhnik
2009-08-13 3:56 ` erik quanstrom
2009-08-13 6:49 ` Daniel Lyons
2009-08-13 10:01 ` Uriel
2009-08-14 4:58 ` Nate S
2009-08-13 8:33 ` Richard Miller
2009-08-13 8:42 ` roger peppe [this message]
2009-08-13 13:43 ` erik quanstrom
2009-08-13 14:27 ` David Leimbach
2009-08-13 15:06 ` roger peppe
2009-08-14 3:41 ` Uriel
2009-08-14 13:19 ` matt
2009-08-17 15:27 ` David Leimbach
2009-08-17 15:44 ` ron minnich
2009-08-17 15:58 ` David Leimbach
2009-08-14 19:08 ` Roman V. Shaposhnik
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=df49a7370908130142h4c82f836n96ef577c01d4d747@mail.gmail.com \
--to=rogpeppe@gmail.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).