aboutsummaryrefslogtreecommitdiff
path: root/src/transport
diff options
context:
space:
mode:
Diffstat (limited to 'src/transport')
-rw-r--r--src/transport/gnunet-service-tng.c15
1 files changed, 13 insertions, 2 deletions
diff --git a/src/transport/gnunet-service-tng.c b/src/transport/gnunet-service-tng.c
index 707fe49a7..a32d1872c 100644
--- a/src/transport/gnunet-service-tng.c
+++ b/src/transport/gnunet-service-tng.c
@@ -32,10 +32,17 @@
32 * (which could be core-data, background-channel traffic, or 32 * (which could be core-data, background-channel traffic, or
33 * transport-to-transport traffic) 33 * transport-to-transport traffic)
34 * 34 *
35 * Implement: 35 * Implement next:
36 * - ACK handling / retransmission 36 * - ACK handling / retransmission
37 * - track RTT, distance, loss, etc. 37 * - track RTT, distance, loss, etc.
38 * - DV data structures, learning, forgetting & using them! 38 * - DV data structures:
39 * + learning
40 * + forgetting
41 * + using them!
42 * - routing of messages (using DV data structures!)
43 * - handling of DV-boxed messages that need to be forwarded
44 * - backchannel message encryption & decryption
45 * -
39 * 46 *
40 * Easy: 47 * Easy:
41 * - use ATS bandwidth allocation callback and schedule transmissions! 48 * - use ATS bandwidth allocation callback and schedule transmissions!
@@ -51,6 +58,10 @@
51 * - if messages are below MTU, consider adding ACKs and other stuff 58 * - if messages are below MTU, consider adding ACKs and other stuff
52 * (requires planning at receiver, and additional MST-style demultiplex 59 * (requires planning at receiver, and additional MST-style demultiplex
53 * at receiver!) 60 * at receiver!)
61 * - could avoid copying body of message into each fragment and keep
62 * fragments as just pointers into the original message and only
63 * fully build fragments just before transmission (optimization, should
64 * reduce CPU and memory use)
54 * 65 *
55 * Design realizations / discussion: 66 * Design realizations / discussion:
56 * - communicators do flow control by calling MQ "notify sent" 67 * - communicators do flow control by calling MQ "notify sent"