X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/5783ed629595652c798bd0052b6e0ea7b1fd70fe..059ffba3002aa86e17392c7f2c884095ab64591b:/doc/gtut-tour-10-rpc.doc
diff --git a/doc/gtut-tour-10-rpc.doc b/doc/gtut-tour-10-rpc.doc
index e57384554e..6591c0fe74 100644
--- a/doc/gtut-tour-10-rpc.doc
+++ b/doc/gtut-tour-10-rpc.doc
@@ -3,11 +3,11 @@
\section GRAS_tut_tour_rpc_toc Table of Contents
- \ref GRAS_tut_tour_rpc_intro
- - \ref GRAS_tut_tour_rpc_use
- - \ref GRAS_tut_tour_rpc_use_declare
- - \ref GRAS_tut_tour_rpc_use_i2a_cb
- - \ref GRAS_tut_tour_rpc_use_a2i_cb
- - \ref GRAS_tut_tour_rpc_use_rest
+ - \ref GRAS_tut_tour_rpc_use
+ - \ref GRAS_tut_tour_rpc_use_declare
+ - \ref GRAS_tut_tour_rpc_use_i2a_cb
+ - \ref GRAS_tut_tour_rpc_use_a2i_cb
+ - \ref GRAS_tut_tour_rpc_use_rest
- \ref GRAS_tut_tour_rpc_recap
@@ -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
@@ -43,7 +44,7 @@ message. In our example, we accept one string in input, and a long in
output for the a2i conversion (a=char 2=to i=integer), and the contrary in
the other direction.
-\dontinclude 10-rpc.c
+\don'tinclude 10-rpc.c
\skip gras_msgtype_declare_rpc
\until long
\until string
@@ -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
*/