X-Git-Url: http://info.iut-bm.univ-fcomte.fr/pub/gitweb/simgrid.git/blobdiff_plain/676756b1101b958d0b55f43a09f3dab421dd9c1f:/doc/gtut-tour-2-simple.doc..b3f448e0ccc0e5e0195bfba380b1ba3a5c5b10b6:/doc/gtut-tour-02-simple.doc

diff --git a/doc/gtut-tour-2-simple.doc b/doc/gtut-tour-02-simple.doc
similarity index 97%
rename from doc/gtut-tour-2-simple.doc
rename to doc/gtut-tour-02-simple.doc
index 3fcfab6751..3dfba8fd4e 100644
--- a/doc/gtut-tour-2-simple.doc
+++ b/doc/gtut-tour-02-simple.doc
@@ -22,7 +22,7 @@ Fortunately, such discrepency will be detected in SG.
 
 We won't convey any payload in this lesson, so we just have to give the name
 of message to declare them:
-\dontinclude 2-simple.c
+\dontinclude 02-simple.c
 \skip gras_msgtype_declare
 \until gras_msgtype_declare
 
@@ -65,7 +65,7 @@ messages, you have to create a so-called <i>client socket</i>. For this, use
 \ref gras_socket_client with the hostname and the port of the process you
 want to contact as arguments. Our client should simply do:
 
-\dontinclude 2-simple.c
+\dontinclude 02-simple.c
 \skip socket_client
 \until socket_client
 
@@ -85,7 +85,7 @@ message, the message type, and a pointer to the actual content of the
 message. The simplest way to retrive a message type from its name is to use
 \ref gras_msgtype_by_name. Since we don't have any payload, this becomes:
 
-\dontinclude 2-simple.c
+\dontinclude 02-simple.c
 \skip msg_send
 \until msg_send
 
@@ -97,7 +97,7 @@ message you received while the last argument is where to put the payload.
 
 Since our server is willing to wait up to 60 seconds for a message, the
 following will do it:
-\dontinclude 2-simple.c
+\dontinclude 02-simple.c
 \skip msg_wait
 \until msg_wait
 
@@ -107,14 +107,14 @@ Here is the complete code of this example. Note the use of the functions
 \ref gras_socket_my_port, \ref gras_socket_peer_name and \ref
 gras_socket_peer_port to retrieve information about who you are connected to.
 
-\include 2-simple.c
+\include 02-simple.c
 
 Here is the output of the simulator. Note that \ref gras_socket_peer_port
 actually returns the port number of the <i>server</i> of the peer. This may
 sound a bit strange to BSD experts, but it is actually really useful: you
 can store this value, and contact your peer afterward passing this number to
 \ref gras_socket_client .
-\include 2-simple.output
+\include 02-simple.output
 
 Here we are, you now know how to exchange messages between peers. There is
 still a large room for improvement, such as adding payload to messages. But