diff options
author | ng0 <ng0@infotropique.org> | 2017-10-26 12:59:47 +0000 |
---|---|---|
committer | ng0 <ng0@infotropique.org> | 2017-10-26 13:00:55 +0000 |
commit | 732816be49f49ec4b3db669b73d817fe5f930803 (patch) | |
tree | 0ac125761c09e66f64b0da41716ee160a5f2f0ba /doc/documentation/gnunet-c-tutorial.texi | |
parent | fea7c5644a6eb4fa9bb68bf201cbf55996ae1c79 (diff) | |
download | gnunet-732816be49f49ec4b3db669b73d817fe5f930803.tar.gz gnunet-732816be49f49ec4b3db669b73d817fe5f930803.zip |
@i{} -> @b{} and @{code} where appropriate
Avoid italics.
Diffstat (limited to 'doc/documentation/gnunet-c-tutorial.texi')
-rw-r--r-- | doc/documentation/gnunet-c-tutorial.texi | 27 |
1 files changed, 14 insertions, 13 deletions
diff --git a/doc/documentation/gnunet-c-tutorial.texi b/doc/documentation/gnunet-c-tutorial.texi index b62db7855..f39c7de64 100644 --- a/doc/documentation/gnunet-c-tutorial.texi +++ b/doc/documentation/gnunet-c-tutorial.texi | |||
@@ -163,7 +163,7 @@ and rerun the @code{gpg --verify-files} command. | |||
163 | @b{Note:}@ | 163 | @b{Note:}@ |
164 | @b{The pub key to sign the 0.10.1 release has been | 164 | @b{The pub key to sign the 0.10.1 release has been |
165 | revoked}. You will get an error message stating that | 165 | revoked}. You will get an error message stating that |
166 | @i{there is no known public key or that it has been revoked}. | 166 | @b{there is no known public key or that it has been revoked}. |
167 | The next release of GNUnet will have a valid signature | 167 | The next release of GNUnet will have a valid signature |
168 | again. We are sorry for the inconvenience this causes. | 168 | again. We are sorry for the inconvenience this causes. |
169 | Another possible source you could use is our | 169 | Another possible source you could use is our |
@@ -171,7 +171,7 @@ Another possible source you could use is our | |||
171 | by every developer. | 171 | by every developer. |
172 | 172 | ||
173 | Now you can extract the tarball and rename the resulting | 173 | Now you can extract the tarball and rename the resulting |
174 | directory to @i{gnunet} which we will be using in the | 174 | directory to @file{gnunet} which we will be using in the |
175 | remainder of this document. | 175 | remainder of this document. |
176 | 176 | ||
177 | @example | 177 | @example |
@@ -713,9 +713,10 @@ marked as ``done'' before their completion. | |||
713 | 713 | ||
714 | An operation is treated as completed when it succeeds or fails. | 714 | An operation is treated as completed when it succeeds or fails. |
715 | Completion of an operation is either conveyed as events through | 715 | Completion of an operation is either conveyed as events through |
716 | @i{controller event callback} or through respective operation | 716 | @dfn{controller event callback} or through respective |
717 | completion callbacks. In functions which support completion | 717 | @dfn{operation completion callbacks}. |
718 | notification through both controller event callback and operation | 718 | In functions which support completion notification |
719 | through both controller event callback and operation | ||
719 | completion callback, first the controller event callback will be | 720 | completion callback, first the controller event callback will be |
720 | called. If the operation is not marked as done in that callback | 721 | called. If the operation is not marked as done in that callback |
721 | or if the callback is given as NULL when creating the operation, | 722 | or if the callback is given as NULL when creating the operation, |
@@ -733,14 +734,14 @@ discouraged as their locations are dynamically created and will be | |||
733 | different among various runs of testbed. To make access to these | 734 | different among various runs of testbed. To make access to these |
734 | configurations easy, testbed API provides the function | 735 | configurations easy, testbed API provides the function |
735 | @code{GNUNET\_TESTBED\_service\_connect()}. This function fetches | 736 | @code{GNUNET\_TESTBED\_service\_connect()}. This function fetches |
736 | the configuration of a given peer and calls the @i{Connect Adapter}. | 737 | the configuration of a given peer and calls the @dfn{Connect Adapter}. |
737 | In the example code, it is the @code{dht\_ca}. A connect adapter is | 738 | In the example code, it is the @code{dht\_ca}. A connect adapter is |
738 | expected to open the connection to the needed service by using the | 739 | expected to open the connection to the needed service by using the |
739 | provided configuration and return the created service connection handle. | 740 | provided configuration and return the created service connection handle. |
740 | Successful connection to the needed service is signaled through | 741 | Successful connection to the needed service is signaled through |
741 | @code{service\_connect\_comp\_cb}. | 742 | @code{service\_connect\_comp\_cb}. |
742 | 743 | ||
743 | A dual to connect adapter is the @i{Disconnect Adapter}. This callback | 744 | A dual to connect adapter is the @dfn{Disconnect Adapter}. This callback |
744 | is called after the connect adapter has been called when the operation | 745 | is called after the connect adapter has been called when the operation |
745 | from @code{GNUNET\_TESTBED\_service\_connect()} is marked as ``done''. | 746 | from @code{GNUNET\_TESTBED\_service\_connect()} is marked as ``done''. |
746 | It has to disconnect from the service with the provided service | 747 | It has to disconnect from the service with the provided service |
@@ -750,8 +751,8 @@ Exercise: Find out how many peers you can run on your system. | |||
750 | 751 | ||
751 | Exercise: Find out how to create a 2D torus topology by changing the | 752 | Exercise: Find out how to create a 2D torus topology by changing the |
752 | options in the configuration file. | 753 | options in the configuration file. |
753 | See @uref{https://gnunet.org/supported-topologies}, then use the | 754 | @xref{Supported Topologies, The GNUnet Reference Documentation ,, gnunet, The GNUnet Reference Documentation}, |
754 | DHT API to store and retrieve values in the network. | 755 | then use the DHT API to store and retrieve values in the network. |
755 | 756 | ||
756 | @node Developing Applications | 757 | @node Developing Applications |
757 | @chapter Developing Applications | 758 | @chapter Developing Applications |
@@ -1105,7 +1106,7 @@ peer to the service: | |||
1105 | 1106 | ||
1106 | @noindent | 1107 | @noindent |
1107 | Note that whatever you return from @code{connects} is given as the | 1108 | Note that whatever you return from @code{connects} is given as the |
1108 | @i{cls} argument to the message handlers for messages from | 1109 | @code{cls} argument to the message handlers for messages from |
1109 | the respective peer. | 1110 | the respective peer. |
1110 | 1111 | ||
1111 | Exercise: Create a service that connects to the @code{CORE}. Then | 1112 | Exercise: Create a service that connects to the @code{CORE}. Then |
@@ -1116,7 +1117,7 @@ callback is invoked. | |||
1116 | @subsection Receiving P2P Messages | 1117 | @subsection Receiving P2P Messages |
1117 | 1118 | ||
1118 | To receive messages from @code{CORE}, you pass the desired | 1119 | To receive messages from @code{CORE}, you pass the desired |
1119 | @i{handlers} to the @code{GNUNET\_CORE\_connect()} function, | 1120 | @code{handlers} to the @code{GNUNET\_CORE\_connect()} function, |
1120 | just as we showed for services. | 1121 | just as we showed for services. |
1121 | 1122 | ||
1122 | It is your responsibility to process messages fast enough or | 1123 | It is your responsibility to process messages fast enough or |
@@ -1132,8 +1133,8 @@ the two peers are connected? Why? | |||
1132 | @node Sending P2P Messages | 1133 | @node Sending P2P Messages |
1133 | @subsection Sending P2P Messages | 1134 | @subsection Sending P2P Messages |
1134 | 1135 | ||
1135 | You can transmit messages to other peers using the @i{mq} you were | 1136 | You can transmit messages to other peers using the @code{mq} you were |
1136 | given during the @code{connect} callback. Note that the @i{mq} | 1137 | given during the @code{connect} callback. Note that the @code{mq} |
1137 | automatically is released upon @code{disconnect} and that you must | 1138 | automatically is released upon @code{disconnect} and that you must |
1138 | not use it afterwards. | 1139 | not use it afterwards. |
1139 | 1140 | ||