We won't convey any payload in this lesson, so we just have to give the name
of message to declare them:
-\dontinclude 02-simple.c
+\don'tinclude 02-simple.c
\skip gras_msgtype_declare
\until gras_msgtype_declare
\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 02-simple.c
+\don'tinclude 02-simple.c
\skip socket_client
\until socket_client
message, the message type (described by its name), and a pointer to the actual content of the
message. Since we don't have any payload, this becomes:
-\dontinclude 02-simple.c
+\don'tinclude 02-simple.c
\skip msg_send
\until msg_send
Since our server is willing to wait up to 60 seconds for a message, the
following will do it:
-\dontinclude 02-simple.c
+\don'tinclude 02-simple.c
\skip msg_wait
\until msg_wait
\section GRAS_tut_tour_simpleexchange_recaping Recaping everything together
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.
+\ref xbt_socket_my_port, \ref xbt_socket_peer_name and \ref
+xbt_socket_peer_port to retrieve information about who you are connected to.
\include 02-simple.c
-Here is the output of the simulator. Note that \ref gras_socket_peer_port
+Here is the output of the simulator. Note that \ref xbt_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
