From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,1eef1e815cf70416 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.238.65 with SMTP id vi1mr574538pbc.7.1339204237287; Fri, 08 Jun 2012 18:10:37 -0700 (PDT) MIME-Version: 1.0 Path: l9ni30988pbj.0!nntp.google.com!news1.google.com!news.glorb.com!feeder.erje.net!news2.arglkargh.de!news.mixmin.net!aioe.org!.POSTED!not-for-mail From: tmoran@acm.org Newsgroups: comp.lang.ada Subject: Re: Distributed Systems Annex, data sharing between programs Date: Sat, 9 Jun 2012 01:10:35 +0000 (UTC) Organization: Aioe.org NNTP Server Message-ID: References: <0d661453-423c-484b-90cd-4e80ffe1db5b@6g2000vbv.googlegroups.com> NNTP-Posting-Host: Lf0Nl3CcQzx+ocHx9cmuGg.user.speranza.aioe.org X-Complaints-To: abuse@aioe.org X-Notice: Filtered by postfilter v. 0.8.2 X-Newsreader: Tom's custom newsreader Date: 2012-06-09T01:10:35+00:00 List-Id: >The solution is to stop thinking in terms of RPC (remote procesure >calls), and start thinking in terms of messages. How about asynchronous remote procedure calls. They just fire-and-forget the parameters/message to a remote procedure. Or in the example of possibly dead targets, use synchronous RPC that handles Communication_Error. But setting up the partition mapping for thousands of partitions might indeed be inappropriate. ;)