From: mquinson Date: Mon, 12 Feb 2007 13:52:02 +0000 (+0000) Subject: Add a link to next lesson, minor improvement X-Git-Tag: v3.3~2232 X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/commitdiff_plain/04e7fb0ffb10e130bf7a7dd3e04e035d48673d78 Add a link to next lesson, minor improvement git-svn-id: svn+ssh://scm.gforge.inria.fr/svn/simgrid/simgrid/trunk@3127 48e7efb5-ca39-0410-a469-dd3cf9ba447f --- diff --git a/doc/gtut-tour-10-rpc.doc b/doc/gtut-tour-10-rpc.doc index e57384554e..00b927462a 100644 --- a/doc/gtut-tour-10-rpc.doc +++ b/doc/gtut-tour-10-rpc.doc @@ -21,8 +21,9 @@ computation. This design is often refered to as "Remote Procedure Call" or RPC for short. It is naturally possible to build RPC exchanges using only one-way messages, -as the ones we used in GRAS so far, but it's a bit awkward. That is why GRAS -provide a support for RPC, as we will now detail. +as the ones we used in GRAS so far, but it's a bit awkward (specially when +the server wants to return a value to the client in a remote function call). +That is why GRAS provide a support for RPC, as we will now detail. \section GRAS_tut_tour_rpc_use Putting rpc into action @@ -96,5 +97,8 @@ The program now reads: Which produces the expected output: \include 10-rpc.output +Now, you know how to send messages, attach callbacks and do RPCs. The next +lesson will learn you the last missing part of the messaging library: +\ref GRAS_tut_tour_explicitwait */