diff options
author | psyc://loupsycedyglgamf.onion/~lynX <ircs://psyced.org/youbroketheinternet> | 2018-06-27 10:59:52 +0000 |
---|---|---|
committer | psyc://loupsycedyglgamf.onion/~lynX <ircs://psyced.org/youbroketheinternet> | 1984-04-04 00:44:04 +0000 |
commit | 96d63458bc11fa18c7d7e334b6509ce6e0196890 (patch) | |
tree | 9d0a5e9b1e11b97c84a1048336fa19ba730f3450 /doc/documentation/chapters/developer.texi | |
parent | 62fa707cf1568a487323f904061a27dcfb0642fa (diff) | |
download | gnunet-96d63458bc11fa18c7d7e334b6509ce6e0196890.tar.gz gnunet-96d63458bc11fa18c7d7e334b6509ce6e0196890.zip |
-docs: the world ain't all male II
Diffstat (limited to 'doc/documentation/chapters/developer.texi')
-rw-r--r-- | doc/documentation/chapters/developer.texi | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/documentation/chapters/developer.texi b/doc/documentation/chapters/developer.texi index 4167c3d62..1f74a8163 100644 --- a/doc/documentation/chapters/developer.texi +++ b/doc/documentation/chapters/developer.texi | |||
@@ -4382,7 +4382,7 @@ If you encounter problems regarding the SDP server (like the SDP server is | |||
4382 | down) you should check out if the D-Bus daemon is running correctly and to | 4382 | down) you should check out if the D-Bus daemon is running correctly and to |
4383 | see if the Bluetooth daemon started correctly(use @code{bluetoothd} tool). | 4383 | see if the Bluetooth daemon started correctly(use @code{bluetoothd} tool). |
4384 | Also, sometimes the SDP service could work but somehow the device couldn't | 4384 | Also, sometimes the SDP service could work but somehow the device couldn't |
4385 | register his service. Use @code{sdptool browse [dev-address]} to see if | 4385 | register its service. Use @code{sdptool browse [dev-address]} to see if |
4386 | the service is registered. There should be a service with the name of the | 4386 | the service is registered. There should be a service with the name of the |
4387 | interface and GNUnet as provider. | 4387 | interface and GNUnet as provider. |
4388 | 4388 | ||
@@ -5453,7 +5453,7 @@ calls: @code{GNUNET_NSE_connect} and @code{GNUNET_NSE_disconnect}. | |||
5453 | The connect call gets a callback function as a parameter and this function | 5453 | The connect call gets a callback function as a parameter and this function |
5454 | is called each time the network agrees on an estimate. This usually is | 5454 | is called each time the network agrees on an estimate. This usually is |
5455 | once per round, with some exceptions: if the closest peer has a late | 5455 | once per round, with some exceptions: if the closest peer has a late |
5456 | local clock and starts spreading his ID after everyone else agreed on a | 5456 | local clock and starts spreading its ID after everyone else agreed on a |
5457 | value, the callback might be activated twice in a round, the second value | 5457 | value, the callback might be activated twice in a round, the second value |
5458 | being always bigger than the first. The default round time is set to | 5458 | being always bigger than the first. The default round time is set to |
5459 | 1 hour. | 5459 | 1 hour. |
@@ -5579,7 +5579,7 @@ is what we are flooding the network with right now. | |||
5579 | At the beginning of each round the peer does the following: | 5579 | At the beginning of each round the peer does the following: |
5580 | 5580 | ||
5581 | @itemize @bullet | 5581 | @itemize @bullet |
5582 | @item calculates his own distance to the target value | 5582 | @item calculates its own distance to the target value |
5583 | @item creates, signs and stores the message for the current round (unless | 5583 | @item creates, signs and stores the message for the current round (unless |
5584 | it has a better message in the "next round" slot which came early in the | 5584 | it has a better message in the "next round" slot which came early in the |
5585 | previous round) | 5585 | previous round) |
@@ -6215,8 +6215,8 @@ So a client has first to retrieve records, merge with existing records | |||
6215 | and then store the result. | 6215 | and then store the result. |
6216 | 6216 | ||
6217 | To perform a lookup operation, the client uses the | 6217 | To perform a lookup operation, the client uses the |
6218 | @code{GNUNET_NAMESTORE_records_store} function. Here he has to pass the | 6218 | @code{GNUNET_NAMESTORE_records_store} function. Here it has to pass the |
6219 | namestore handle, the private key of the zone and the label. He also has | 6219 | namestore handle, the private key of the zone and the label. It also has |
6220 | to provide a callback function which will be called with the result of | 6220 | to provide a callback function which will be called with the result of |
6221 | the lookup operation: | 6221 | the lookup operation: |
6222 | the zone for the records, the label, and the records including the | 6222 | the zone for the records, the label, and the records including the |
@@ -6239,7 +6239,7 @@ by NAMESTORE. | |||
6239 | Here a client uses the @code{GNUNET_NAMESTORE_zone_iteration_start} | 6239 | Here a client uses the @code{GNUNET_NAMESTORE_zone_iteration_start} |
6240 | function and passes the namestore handle, the zone to iterate over and a | 6240 | function and passes the namestore handle, the zone to iterate over and a |
6241 | callback function to call with the result. | 6241 | callback function to call with the result. |
6242 | If the client wants to iterate over all the, he passes NULL for the zone. | 6242 | If the client wants to iterate over all the WHAT!? FIXME, it passes NULL for the zone. |
6243 | A @code{GNUNET_NAMESTORE_ZoneIterator} handle is returned to be used to | 6243 | A @code{GNUNET_NAMESTORE_ZoneIterator} handle is returned to be used to |
6244 | continue iteration. | 6244 | continue iteration. |
6245 | 6245 | ||
@@ -6935,7 +6935,7 @@ number of iterations). | |||
6935 | The receiver of the message removes all elements from its local set that | 6935 | The receiver of the message removes all elements from its local set that |
6936 | do not pass the Bloom filter test. | 6936 | do not pass the Bloom filter test. |
6937 | It then checks if the set size of the sender and the XOR over the keys | 6937 | It then checks if the set size of the sender and the XOR over the keys |
6938 | match what is left of his own set. If they do, he sends a | 6938 | match what is left of its own set. If they do, it sends a |
6939 | @code{GNUNET_MESSAGE_TYPE_SET_INTERSECTION_P2P_DONE} back to indicate | 6939 | @code{GNUNET_MESSAGE_TYPE_SET_INTERSECTION_P2P_DONE} back to indicate |
6940 | that the latest set is the final result. | 6940 | that the latest set is the final result. |
6941 | Otherwise, the receiver starts another Bloom filter exchange, except | 6941 | Otherwise, the receiver starts another Bloom filter exchange, except |
@@ -8239,7 +8239,7 @@ When a revocation is performed, the revocation is first of all | |||
8239 | disseminated by flooding the overlay network. | 8239 | disseminated by flooding the overlay network. |
8240 | The goal is to reach every peer, so that when a peer needs to check if a | 8240 | The goal is to reach every peer, so that when a peer needs to check if a |
8241 | key has been revoked, this will be purely a local operation where the | 8241 | key has been revoked, this will be purely a local operation where the |
8242 | peer looks at his local revocation list. Flooding the network is also the | 8242 | peer looks at its local revocation list. Flooding the network is also the |
8243 | most robust form of key revocation --- an adversary would have to control | 8243 | most robust form of key revocation --- an adversary would have to control |
8244 | a separator of the overlay graph to restrict the propagation of the | 8244 | a separator of the overlay graph to restrict the propagation of the |
8245 | revocation message. Flooding is also very easy to implement --- peers that | 8245 | revocation message. Flooding is also very easy to implement --- peers that |