X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=TODO;h=c3b8aa051f382590243f89742b9300c1845d3e4e;hb=9c0e92ec7637b081d35582adfe775f8be7b1f2a3;hp=2de4519b6d54ebfc812652d372ae279b0d0af222;hpb=cccf428c27fc15e0d8f084d1d5241e5e308993b0;p=oweals%2Fgnunet.git

diff --git a/TODO b/TODO
index 2de4519b6..c3b8aa051 100644
--- a/TODO
+++ b/TODO
@@ -8,52 +8,23 @@ away), in order in which they will likely be done:
 * TRACEKIT
 * FRAGMENTATION [Ji Lu]
 * HTTP transport
-* MySQL / Postgres plugins (datastore, datacache) [Radhika]
+* MySQL / Postgres plugins (datastore, datacache)
 * UPNP [Milan]
+* ARM [Safey]
 
 Urgent items (before announcing ng.gnunet.org):
-* topology
-  - needs testing
-* hostlist
-  - test fails (peers don't connect quickly, could be topology issue)
-
-* CORE:
-  - soliciting traffic for clients that registered for it is not implemented
-    (in the service, client API supports GNUNET_MESSAGE_TYPE_CORE_SOLICIT_TRAFFIC
-     but never receives any such messages); how to avoid busy-waiting here
-     is a good question (solicit => nothing, when to solicit again???)
-* TRANSPORT:
-  - crashes:
-(gdb) ba
-#0  0x00007ffff5d0d3d4 in disconnect_session (session=0x656700)
-    at plugin_transport_tcp.c:797
-#1  0x00007ffff5d0d74c in session_try_connect (cls=0x656700, peer=0x0, 
-    hello=0x0, trust=0) at plugin_transport_tcp.c:990
-#2  0x00007ffff7bdf26e in info_handler (cls=0x6306e0, msg=0x7fffffffda60)
-    at peerinfo_api.c:180
-#3  0x00007ffff79b0452 in receive_task (cls=0x69ec40, tc=0x7fffffffdb00)
-    at client.c:491
-#4  0x00007ffff79cccaa in run_ready (sched=0x7fffffffdb70) at scheduler.c:482
-#5  0x00007ffff79cd0ba in GNUNET_SCHEDULER_run (
-    task=0x7ffff79d1898 <service_task>, task_cls=0x7fffffffde10)
-    at scheduler.c:609
-#6  0x00007ffff79d27e1 in GNUNET_SERVICE_run (argc=3, argv=0x7fffffffe028, 
-    serviceName=0x405e6b "transport", opt=GNUNET_SERVICE_OPTION_NONE, 
-    task=0x4055c9 <run>, task_cls=0x0) at service.c:1345
-#7  0x0000000000405870 in main (argc=3, argv=0x7fffffffe028)
-    at gnunet-service-transport.c:2784
-
-
 * FS (basic anonymous FS only)
-  - implement FS service (P2P operations)
-    + how to send queries (soliciting is not there in core; do we
-      also want to do pushing sometimes?)
-    + need to bound queueing of replies for other peers    
   - 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
 
 
@@ -62,13 +33,27 @@ Urgent items (before announcing ng.gnunet.org):
   - load: need way to determine network load (up/down)
   - trust: need *fast* way to check/update trust in peers
            (async peerinfo would not be right)
-  - OS: existing waitpid call is not nice (not integratable with scheduler! fix this!)
+* TRANSPORT:
+  - 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
+  - synchronous/asynchronous API (& implementation) is not nice;
+    => provide notification-based API
   - does not seem to work with timeouts (especially if service is not running)
 * ARM:
   - need to get rid of synchronous API for service starts (cause all kinds of problems)
-    [=> eliminate for need to tell ARM about service starts most of the time!]
+    [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
+* HELLO:
+  - need function to test "equivalency" of HELLOs; use in topology!
+* TOPOLOGY:
+  - needs more testing (especially F2F topology)
+* CORE:
+  - needs more testing
 * Module features to implement:
   - advanced FS API parts
     + namespaces: fundamental namespace API
@@ -85,8 +70,8 @@ Urgent items (before announcing ng.gnunet.org):
     + gnunet-download (many options)
     + gnunet-directory (man page, options)
     + gnunet-pseudonym (all of it)
-    + gnunet-service-fs (remove failing on-demand blocks, many other nitpicks/features/optimizations)
-    + datastore: do active migration support here?
+    + gnunet-service-fs (remove failing on-demand blocks, stats, hot-path routing, load-based routing, nitpicks)
+    + datastore: do active migration support here?   
   - implement adv. FS testcases 
     + getopt API
     + insert: sblocks, loc uris
@@ -190,3 +175,8 @@ Urgent items (before announcing ng.gnunet.org):
   (add options to gnunet-search / gnunet-download to limit search to local peer)
 * STATISTICS:
   - should use BIO instead of mmap
+* PEERINFO:
+  - expire 'ancient' HELLOs (those without valid addresses AND that 
+    we have not 'used' (for their public keys) in a while; need a way
+    to track actual 'use')
+  - make sue we also trigger notifications whenever HELLOs expire