From: Roman Shaposhnik <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Thrift RPC
Date: Wed, 12 Aug 2009 21:33:03 -0700 [thread overview]
Message-ID: <9D912E66-C3DA-4F41-914D-2AF77BC4BEC8@sun.com> (raw)
In-Reply-To: <Pine.BSI.4.64.0908121747050.20861@malasada.lava.net>
On Aug 12, 2009, at 8:49 PM, Tim Newsham wrote:
>> 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) and you
>> really shouldn't be made to figure out how large is the integer
>> on a host foo?
>
> Just because the world is full of XML zealots does not mean that XDR
> (ONC RPC), NDR (DCE RPC)
Well, they sure smell that way. The only non trivial application of
SUN RPC still
in existence that I know of is NFS (plus its evil twins). I would be
very curious
to know if you have examples of interesting apps using both types of
RPC.
> and others are dead. Neither of these makes you figure out how
> large the integer on host foo is (thats half the point).
What's your method of portably stuffing a *native* 64 int (the one
from the ILP64 type of
ABIs)?
> I personally like the XDR standard (I can do without NDR and BER/DER).
Here's an honest question: do you really like debugging rpcgen emitted
code?
Thanks,
Roman.
next prev parent reply other threads:[~2009-08-13 4:33 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 [this message]
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
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=9D912E66-C3DA-4F41-914D-2AF77BC4BEC8@sun.com \
--to=rvs@sun.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).