drop

[oweals/gnunet.git] / TODO

diff --git a/TODO b/TODO
index 2de4519b6d54ebfc812652d372ae279b0d0af222..992f61f8070563cd1cfa7feb0e574371776b548a 100644 (file)
--- a/TODO
+++ b/TODO
@@ -12,38 +12,40 @@ away), in order in which they will likely be done:
 * UPNP [Milan]
 
 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???)
+* UTIL:
+  - provide higher-level convenience API for servers/services that
+    need to send a stream of notifications to clients; instead
+    of having each service queue messages and "send when ready", 
+    simply have a way to add a client to the notification set
+    and to 'notify client' or 'notify all clients'
+    (useful for peerinfo (new hellos), transport (our hello; blacklist), 
+     core (misc monitoring features), statistics (change notifications)
+     and likely others)
+  - server/service API change for ARM inetd'ing
+    (listen as well as support for start with multiple, already
+     bound & listening sockets!)
 * 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
-
-
+  - main service not implemented [Nate]
+  - blacklist not implemented [Christian]
+  - testcases crash & burn (no surprise)
+* CORE:
+  - request disconnect not implemented [Christian]
+  - various notification options not implemented [Christian]
+  - test currently fails spectacularly [segv of transport service]
+    => need transport to work first!
+  - request connect not working [Christian, need transport first]
+* PEERINFO:
+  - make sue we also trigger notifications whenever HELLOs expire
+* TOPOLOGY:
+  - needs testing [need transport first]
+* TESTING:
+  - check that 'GNUNET_TRANSPORT_get_hello' is associated with
+    a cancel request wherever appropriate (other testcases
+    in particular!) [Christian]
+* HOSTLIST:
+  - test fails (looks like it works, but that's because of a bad
+    connectivity notification; somehow core is unable to send
+    messages successfully via transport) [need transport first]
 * FS (basic anonymous FS only)
   - implement FS service (P2P operations)
     + how to send queries (soliciting is not there in core; do we
@@ -69,6 +71,10 @@ Urgent items (before announcing ng.gnunet.org):
 * 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!]
+* HELLO:
+  - need function to test "equivalency" of HELLOs; use in topology!
+* CORE:
+  - outbound message monitoring not supported
 * Module features to implement:
   - advanced FS API parts
     + namespaces: fundamental namespace API