* 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 (gnunet-service-core crashes -- sometimes; with memory corruption!)
-* 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???)
+ - 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
projects / oweals / gnunet.git / blobdiff