ifdef instead of if

[oweals/gnunet.git] / TODO

diff --git a/TODO b/TODO
index 1c06ef57e25d58b0d84c48967ed8b7646d5c91a9..c3b8aa051f382590243f89742b9300c1845d3e4e 100644 (file)
--- a/TODO
+++ b/TODO
@@ -15,10 +15,16 @@ away), in order in which they will likely be done:
 Urgent items (before announcing ng.gnunet.org):
 * FS (basic anonymous FS only)
   - test multi-peer search/download
+    + existing bandwidth-reservation code does not work with FS: don't get
+      DBLOCK size bandwidth for reply for a while => trouble for testcase
+      => need to more aggressively increase bandwidth per connection 
+      => need to check that bandwidth is assigned properly to begin with
+    + Even with bandwidth-reservation code restricted, message is not
+      delivered to other core/peer/fs.  Why?
+    + Same query is sent to the same peer in rather rapid succession (10x/minute?),
+      should tune code to reduce repetition...
 * new webpage
   - run peer => have a 0.9.x hostlist
-  - improve basic documentation (configure, dependencies, what works, etc.)
-  - write minimal welcome/introduction to 0.9.x-development/webpage/status
 => Deploy(able) development network
 
 
@@ -31,6 +37,10 @@ Urgent items (before announcing ng.gnunet.org):
   - disconnect notifications from TCP not always as nice as we might want
     them to be (but how can we do this cleanly given that UDP is connectionless?)
   - TCP not used bi-directionally (especially important also for PONG!)
+  - hostlist testcase shows that (randomly) we jump to an address that
+    seems to be a plugin function *after* the plugin has been unloaded
+    (directly from scheduler); check that *all* plugin tasks are cancelled
+    after plugin is unloaded! (need better testcases for that...)
 * STATISTICS:
   - synchronous/asynchronous API (& implementation) is not nice;
     => provide notification-based API