From 35e5d64293c8b35f36f0eb6336d52321a02fcf80 Mon Sep 17 00:00:00 2001 From: Christian Grothoff Date: Tue, 4 Jun 2013 11:23:36 +0000 Subject: [PATCH] -remarks on mesh api --- src/include/gnunet_mesh2_service.h | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/include/gnunet_mesh2_service.h b/src/include/gnunet_mesh2_service.h index 6ab3f86a0..553838afd 100644 --- 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 -- 2.25.1