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,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.182.186.105 with SMTP id fj9mr1602944obc.5.1383770427735; Wed, 06 Nov 2013 12:40:27 -0800 (PST) X-Received: by 10.49.105.33 with SMTP id gj1mr82512qeb.32.1383770427709; Wed, 06 Nov 2013 12:40:27 -0800 (PST) Path: border2.nntp.dca.giganews.com!nntp.giganews.com!news.snarked.org!newsfeed.news.ucla.edu!usenet.stanford.edu!o2no22941507qas.0!news-out.google.com!9ni14413qaf.0!nntp.google.com!i2no13968246qav.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Wed, 6 Nov 2013 12:40:27 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=93.37.80.0; posting-account=9fwclgkAAAD6oQ5usUYhee1l39geVY99 NNTP-Posting-Host: 93.37.80.0 References: <19b9cc6b-28a4-45e4-939c-7720ae5666b9@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <3ca100fa-0d63-4ec6-80c7-bf8dba658d90@googlegroups.com> Subject: Re: Question about asynchronous calls From: mockturtle Injection-Date: Wed, 06 Nov 2013 20:40:27 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: number.nntp.dca.giganews.com comp.lang.ada:183787 Date: 2013-11-06T12:40:27-08:00 List-Id: >=20 > Asynchronous calls is for calls that do not expect a returned value (no > functions, no out parameters). The only thing you loose is that > exceptions raised on the server side are not transmitted. >=20 > If you need a return channel, use synchronous calls. Asynchronous calls > are an optimization: you don't wait for the result if you don't expect > any result. >=20 I understand and agree. However, I was thinking about a case where you hav= e some fairly long computation done on a remote node and the task on the lo= cal node can do something else while wait for the result. So, it could do = an asynchronous call, carry some other stuff on and then query for the resu= lt. However, I guess that in most of the cases it would be simpler to have= another task on the local node doing the "something else" while the calle= r waits for the result. In the end, it was mostly academic curiosity...=20 Thank you Riccardo