* UPNP [Milan]
Urgent items (before announcing ng.gnunet.org):
+* CORE:
+ - update core API to reflect changes to transport API
+ (need to pass distance to clients!)
+ - test currently fails spectacularly
+ - request disconnect not implemented (needs better transport API)
* topology
- - needs testing
+ - (forced) disconnect does not work (also CORE API issue)
+ - needs testing (not sure the current testcase does much...)
+* testing:
+ - timeout_hello_task is not used but should be (so we can fail
+ properly)
+ - check that 'GNUNET_TRANSPORT_get_hello' is associated with
+ a TIMEOUT task wherever else appropriate (other testcases
+ in particular!)
* 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
-
-
+ - 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)
* FS (basic anonymous FS only)
- implement FS service (P2P operations)
+ how to send queries (soliciting is not there in core; do we
* 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