-remarks on mesh api

diff --git a/src/include/gnunet_mesh2_service.h b/src/include/gnunet_mesh2_service.h
index 6ab3f86a03f1f5737a28aa26e71d28a5ce57359a..553838afd0805578b5396a9276aefcbca564d287 100644 (file)
--- a/src/include/gnunet_mesh2_service.h
+++ b/src/include/gnunet_mesh2_service.h
@@ -150,6 +150,10 @@ typedef void (GNUNET_MESH_TunnelEndHandler) (void *cls,
 /**
  * Connect to the mesh service.
  *
+ * FIXME: flow control is impossible with this API, as the handlers cannot
+ * tell mesh that they are currently too busy to receive more data.
+ * We need something equivalent to 'GNUNET_SERVER_receive_done ()' to do that.
+ *
  * @param cfg configuration to use
  * @param cls closure for the various callbacks that follow
  *            (including handlers in the handlers array)
@@ -189,6 +193,10 @@ GNUNET_MESH_disconnect (struct GNUNET_MESH_Handle *handle);
  * Create a new tunnel (we're initiator and will be allowed to add/remove peers
  * and to broadcast).
  *
+ * FIXME: API quirk: why do I need to be listening just to create an
+ * outbound tunnel? We could pass the 'cfg' plus the handlers here
+ * instead.
+ *
  * @param h mesh handle
  * @param tunnel_ctx client's tunnel context to associate with the tunnel
  * @param peer peer identity the tunnel should go to