aboutsummaryrefslogtreecommitdiff
path: root/src/cadet/TODO
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2017-01-30 16:03:09 +0100
committerChristian Grothoff <christian@grothoff.org>2017-01-30 16:03:09 +0100
commit1b1b7802b1c44baa2cc8ded909e6616e98197d05 (patch)
tree2a9644e2b986ca7cd0260dca1f7435dd54c1062f /src/cadet/TODO
parent8b92d9a2c651d753f756aba5710b6d59ee0f24a1 (diff)
downloadgnunet-1b1b7802b1c44baa2cc8ded909e6616e98197d05.tar.gz
gnunet-1b1b7802b1c44baa2cc8ded909e6616e98197d05.zip
mark as done
Diffstat (limited to 'src/cadet/TODO')
-rw-r--r--src/cadet/TODO6
1 files changed, 1 insertions, 5 deletions
diff --git a/src/cadet/TODO b/src/cadet/TODO
index 317695a5b..bc2451b99 100644
--- a/src/cadet/TODO
+++ b/src/cadet/TODO
@@ -1,8 +1,7 @@
1- URGENT: Congestion/flow control (CHANNEL): 1- URGENT: Congestion/flow control (CHANNEL):
2 + estimate max bandwidth using bursts and use to for CONGESTION CONTROL! 2 + estimate max bandwidth using bursts and use to for CONGESTION CONTROL!
3 (and figure out how/where to use this!) 3 (and figure out how/where to use this!)
4 + calculate current RTT if possible, use that for initial retransmissions 4 + get current RTT from connection; use that for initial retransmissions!
5 (NOTE: needs us to learn which connection the tunnel uses for the message!)
6 + figure out flow control without ACKs (unreliable traffic!) 5 + figure out flow control without ACKs (unreliable traffic!)
7 6
8- HIGH: revisit message buffer, have global buffer instead per-route, but then 7- HIGH: revisit message buffer, have global buffer instead per-route, but then
@@ -25,9 +24,6 @@
25 24
26- OPTIMIZATION: proper connection evaluation during connection management: 25- OPTIMIZATION: proper connection evaluation during connection management:
27 + PATHS: path desirability score calculations are not done 26 + PATHS: path desirability score calculations are not done
28 + CONNECTION: keep per-connection performance metrics;
29 in particular, interact with channel (!) to see
30 if we get ACKs indicating successful payload delivery.
31 + TUNNELS: 27 + TUNNELS:
32 * when managing connections, distinguish those that 28 * when managing connections, distinguish those that
33 have (recently) had traffic from those that were 29 have (recently) had traffic from those that were