diff options
Diffstat (limited to 'doc/tutorial/tutorial.texi')
-rw-r--r-- | doc/tutorial/tutorial.texi | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/tutorial/tutorial.texi b/doc/tutorial/tutorial.texi index e1d70c492..0a011c0c8 100644 --- a/doc/tutorial/tutorial.texi +++ b/doc/tutorial/tutorial.texi | |||
@@ -282,7 +282,7 @@ Assuming all dependencies are installed, the following commands will | |||
282 | compile and install GNUnet in your home directory. You can specify the | 282 | compile and install GNUnet in your home directory. You can specify the |
283 | directory where GNUnet will be installed by changing the | 283 | directory where GNUnet will be installed by changing the |
284 | @code{--prefix} value when calling @command{./configure}. If | 284 | @code{--prefix} value when calling @command{./configure}. If |
285 | you do not specifiy a prefix, GNUnet is installed in the directory | 285 | you do not specify a prefix, GNUnet is installed in the directory |
286 | @file{/usr/local}. When developing new applications you may want | 286 | @file{/usr/local}. When developing new applications you may want |
287 | to enable verbose logging by adding @code{--enable-logging=verbose}: | 287 | to enable verbose logging by adding @code{--enable-logging=verbose}: |
288 | 288 | ||
@@ -940,7 +940,7 @@ with the service, a connection must be created: | |||
940 | As a result a @code{GNUNET\_MQ\_Handle} is returned | 940 | As a result a @code{GNUNET\_MQ\_Handle} is returned |
941 | which can to used henceforth to transmit messages to the service. | 941 | which can to used henceforth to transmit messages to the service. |
942 | The complete MQ API can be found in @file{gnunet\_mq\_lib.h}. | 942 | The complete MQ API can be found in @file{gnunet\_mq\_lib.h}. |
943 | The @code{hanlders} array in the example above is incomplete. | 943 | The @code{handlers} array in the example above is incomplete. |
944 | Here is where you will define which messages you expect to | 944 | Here is where you will define which messages you expect to |
945 | receive from the service, and which functions handle them. | 945 | receive from the service, and which functions handle them. |
946 | The @code{error\_cb} is a function that is to be called whenever | 946 | The @code{error\_cb} is a function that is to be called whenever |
@@ -1060,7 +1060,7 @@ functions, typically called @code{run}, @code{client\_connect\_cb} and | |||
1060 | @code{client\_disconnect\_cb} as well as an array of message handlers | 1060 | @code{client\_disconnect\_cb} as well as an array of message handlers |
1061 | that will be called for incoming messages from clients. | 1061 | that will be called for incoming messages from clients. |
1062 | 1062 | ||
1063 | A minimal version of the three central service funtions would look | 1063 | A minimal version of the three central service functions would look |
1064 | like this: | 1064 | like this: |
1065 | 1065 | ||
1066 | @example | 1066 | @example |
@@ -1093,7 +1093,7 @@ forget to call @code{GNUNET\_SERVICE\_client\_continue()}? | |||
1093 | @node Interacting directly with other Peers using the CORE Service | 1093 | @node Interacting directly with other Peers using the CORE Service |
1094 | @section Interacting directly with other Peers using the CORE Service | 1094 | @section Interacting directly with other Peers using the CORE Service |
1095 | 1095 | ||
1096 | FIXME: This section still needs to be updated to the lastest API! | 1096 | FIXME: This section still needs to be updated to the latest API! |
1097 | 1097 | ||
1098 | One of the most important services in GNUnet is the @code{CORE} service | 1098 | One of the most important services in GNUnet is the @code{CORE} service |
1099 | managing connections between peers and handling encryption between peers. | 1099 | managing connections between peers and handling encryption between peers. |
@@ -1349,7 +1349,7 @@ sent. This does not guarantee that the data is accessible to others peers, | |||
1349 | or even that is has been stored, only that the service has requested to | 1349 | or even that is has been stored, only that the service has requested to |
1350 | a neighboring peer the retransmission of the PUT request towards its final | 1350 | a neighboring peer the retransmission of the PUT request towards its final |
1351 | destination. Currently there is no feedback about whether or not the data | 1351 | destination. Currently there is no feedback about whether or not the data |
1352 | has been sucessfully stored or where it has been stored. In order to | 1352 | has been successfully stored or where it has been stored. In order to |
1353 | improve the availablilty of the data and to compensate for possible | 1353 | improve the availablilty of the data and to compensate for possible |
1354 | errors, peers leaving and other unfavorable events, just make several | 1354 | errors, peers leaving and other unfavorable events, just make several |
1355 | PUT requests! | 1355 | PUT requests! |
@@ -1504,7 +1504,7 @@ GET request, a PUT request or a response (a reply to a GET). | |||
1504 | Since the different events have different associated data, | 1504 | Since the different events have different associated data, |
1505 | the API gets 3 different callbacks (one for each message type) | 1505 | the API gets 3 different callbacks (one for each message type) |
1506 | and optional type and key parameters, to allow for filtering of | 1506 | and optional type and key parameters, to allow for filtering of |
1507 | messages. When an event happens, the appropiate callback is | 1507 | messages. When an event happens, the appropriate callback is |
1508 | called with all the information about the event. | 1508 | called with all the information about the event. |
1509 | 1509 | ||
1510 | @example | 1510 | @example |