gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [gnunet] branch master updated: note on next steps


From: gnunet
Subject: [GNUnet-SVN] [gnunet] branch master updated: note on next steps
Date: Sun, 05 May 2019 14:09:41 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a commit to branch master
in repository gnunet.

The following commit(s) were added to refs/heads/master by this push:
     new da2a7dd65 note on next steps
da2a7dd65 is described below

commit da2a7dd658fa766a71444297051854b166b80fc0
Author: Christian Grothoff <address@hidden>
AuthorDate: Sun May 5 14:09:22 2019 +0200

    note on next steps
---
 src/transport/gnunet-service-tng.c | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/src/transport/gnunet-service-tng.c 
b/src/transport/gnunet-service-tng.c
index ab9159963..df0303571 100644
--- a/src/transport/gnunet-service-tng.c
+++ b/src/transport/gnunet-service-tng.c
@@ -25,8 +25,10 @@
  * TODO:
  * Implement next:
  * - add (more) logging
- * - change transport-core API to specify transmission preferences (latency,
- *   reliability, etc.) per message!
+ * - realize transport-to-transport flow control (needed in case
+ *   communicators do not offer flow control).  Note that we may not
+ *   want to simply delay the ACKs as that may cause unnecessary
+ *   re-transmissions. => Introduce proper flow and congestion window(s)!
  * - review retransmission logic, right now there is no smartness there!
  *   => congestion control, flow control, etc [PERFORMANCE-BASICS]
  *

-- 
To stop receiving notification emails like this one, please contact
address@hidden



reply via email to

[Prev in Thread] Current Thread [Next in Thread]