gnunet-svn
[Top][All Lists]
Advanced

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

[GNUnet-SVN] [gnunet] branch master updated: planning ahead


From: gnunet
Subject: [GNUnet-SVN] [gnunet] branch master updated: planning ahead
Date: Sat, 26 Jan 2019 18:15:22 +0100

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 9830ef2bd planning ahead
9830ef2bd is described below

commit 9830ef2bd3cdcdda93a51cdae56f19ee80f53fc8
Author: Christian Grothoff <address@hidden>
AuthorDate: Sat Jan 26 18:15:17 2019 +0100

    planning ahead
---
 src/transport/gnunet-service-tng.c | 15 +++++++++++++--
 1 file 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 @@
  *      (which could be core-data, background-channel traffic, or
  *       transport-to-transport traffic)
  *
- * Implement:
+ * Implement next:
  * - ACK handling / retransmission 
  * - track RTT, distance, loss, etc.
- * - DV data structures, learning, forgetting & using them!
+ * - DV data structures:
+ *   + learning
+ *   + forgetting 
+ *   + using them!
+ * - routing of messages (using DV data structures!)
+ * - handling of DV-boxed messages that need to be forwarded
+ * - backchannel message encryption & decryption
+ * - 
  *
  * Easy:
  * - use ATS bandwidth allocation callback and schedule transmissions!
@@ -51,6 +58,10 @@
  * - if messages are below MTU, consider adding ACKs and other stuff
  *   (requires planning at receiver, and additional MST-style demultiplex
  *    at receiver!)
+ * - could avoid copying body of message into each fragment and keep
+ *   fragments as just pointers into the original message and only 
+ *   fully build fragments just before transmission (optimization, should
+ *   reduce CPU and memory use)
  *
  * Design realizations / discussion:
  * - communicators do flow control by calling MQ "notify sent"

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



reply via email to

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