aboutsummaryrefslogtreecommitdiff
path: root/src/transport/gnunet-service-tng.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/transport/gnunet-service-tng.c')
-rw-r--r--src/transport/gnunet-service-tng.c6
1 files changed, 5 insertions, 1 deletions
diff --git a/src/transport/gnunet-service-tng.c b/src/transport/gnunet-service-tng.c
index 59575da79..4e8947237 100644
--- a/src/transport/gnunet-service-tng.c
+++ b/src/transport/gnunet-service-tng.c
@@ -40,7 +40,7 @@
40 * whatever else we could reach. 40 * whatever else we could reach.
41 * - AcknowledgementUUIDPs are overkill with 256 bits (128 would do) 41 * - AcknowledgementUUIDPs are overkill with 256 bits (128 would do)
42 * => Need 128 bit hash map though! [BANDWIDTH, MEMORY] 42 * => Need 128 bit hash map though! [BANDWIDTH, MEMORY]
43 * - queue_send_msg and route_message both by API design have to make copies 43 * - queue_send_msg by API design has to make a copy
44 * of the payload, and route_message on top of that requires a malloc/free. 44 * of the payload, and route_message on top of that requires a malloc/free.
45 * Change design to approximate "zero" copy better... [CPU] 45 * Change design to approximate "zero" copy better... [CPU]
46 * - could avoid copying body of message into each fragment and keep 46 * - could avoid copying body of message into each fragment and keep
@@ -56,6 +56,10 @@
56 * triggering an explicit validation mechansim ourselves, specifically routing 56 * triggering an explicit validation mechansim ourselves, specifically routing
57 * a challenge-response message over the path [ROUTING] 57 * a challenge-response message over the path [ROUTING]
58 * - Track ACK losses based on ACK-counter [ROUTING] 58 * - Track ACK losses based on ACK-counter [ROUTING]
59 * - Fragments send over a reliable channel could do without the
60 * AcknowledgementUUIDP altogether, as they won't be acked! [BANDWIDTH]
61 * (-> have 2nd type of acknowledgment message; low priority, as we
62 * do not have an MTU-limited *reliable* communicator)
59 * 63 *
60 * Design realizations / discussion: 64 * Design realizations / discussion:
61 * - communicators do flow control by calling MQ "notify sent" 65 * - communicators do flow control by calling MQ "notify sent"