Next: , Previous: , Up: Using the DHT   [Contents]

4.7.2 Obtaining data from the DHT

As we saw in the previous example, the DHT works in an asynchronous mode. Each request to the DHT is executed “in the background” and the API calls return immediately. In order to receive results from the DHT, the API provides a callback. Once started, the request runs in the service, the service will try to get as many results as possible (filtering out duplicates) until the timeout expires or we explicitly stop the request. It is possible to give a “forever” timeout with GNUNET\_TIME\_UNIT\_FOREVER\_REL.

If we give a route option GNUNET\_DHT\_RO\_RECORD\_ROUTE the callback will get a list of all the peers the data has travelled, both on the PUT path and on the GET path.

static void
get_result_iterator (void *cls, struct GNUNET_TIME_Absolute expiration,
                     const struct GNUNET_HashCode *key,
                     const struct GNUNET_PeerIdentity *get_path,
                     unsigned int get_path_length,
                     const struct GNUNET_PeerIdentity *put_path,
                     unsigned int put_path_length,
                     enum GNUNET_BLOCK_Type type, size_t size,
                     const void *data)
  // Optionally:
  GNUNET_DHT_get_stop (get_handle);

get_handle =
      GNUNET_DHT_get_start (dht_handle,

Exercise: Store a value in the DHT and after a while retrieve it. Show the IDs of all the peers the requests have gone through. In order to convert a peer ID to a string, use the function GNUNET\_i2s. Pay attention to the route option parameters in both calls!