aboutsummaryrefslogtreecommitdiff
path: root/src/mesh/mesh_api.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/mesh/mesh_api.c')
-rw-r--r--src/mesh/mesh_api.c9
1 files changed, 7 insertions, 2 deletions
diff --git a/src/mesh/mesh_api.c b/src/mesh/mesh_api.c
index 51696e4e2..be2ec277d 100644
--- a/src/mesh/mesh_api.c
+++ b/src/mesh/mesh_api.c
@@ -2007,11 +2007,18 @@ GNUNET_MESH_tunnel_buffer (struct GNUNET_MESH_Tunnel *tunnel, int buffer)
2007 send_packet (h, &msg.header, NULL); 2007 send_packet (h, &msg.header, NULL);
2008} 2008}
2009 2009
2010
2010/** 2011/**
2011 * Request that a peer should be added to the tunnel. The existing 2012 * Request that a peer should be added to the tunnel. The existing
2012 * connect handler will be called ONCE with either success or failure. 2013 * connect handler will be called ONCE with either success or failure.
2013 * This function should NOT be called again with the same peer before the 2014 * This function should NOT be called again with the same peer before the
2014 * connect handler is called. 2015 * connect handler is called.
2016 * FIXME: I think the above documentation is false. I think it should
2017 * read: "The connect handler will be called once the peer was actually
2018 * successfully added to the multicast group. This function should
2019 * not be called twice for the same peer (unless, of course,
2020 * the peer was removed using GNUNET_MESH_peer_Request_connect_del in
2021 * the meantime).
2015 * 2022 *
2016 * @param tunnel handle to existing tunnel 2023 * @param tunnel handle to existing tunnel
2017 * @param peer peer to add 2024 * @param peer peer to add
@@ -2043,8 +2050,6 @@ GNUNET_MESH_peer_request_connect_add (struct GNUNET_MESH_Tunnel *tunnel,
2043 msg.tunnel_id = htonl (tunnel->tid); 2050 msg.tunnel_id = htonl (tunnel->tid);
2044 msg.peer = *peer; 2051 msg.peer = *peer;
2045 send_packet (tunnel->mesh, &msg.header, tunnel); 2052 send_packet (tunnel->mesh, &msg.header, tunnel);
2046
2047 return;
2048} 2053}
2049 2054
2050 2055