Implementable right now (but not necessarily important), with caveats
(unavailable components that will limit what can be implemented right
away), in order in which they will likely be done:
-* TESTING [Nate]
+* TESTING-TESTBED [Nate]
* SETUP
-* DV (distributed testing not available) [Nate]
-* TBENCH (distributed testing not available)
-* TRACEKIT (distributed testing not available)
+* DV [Nate]
+* TBENCH
+* TRACEKIT
* FRAGMENTATION [Ji Lu]
* HTTP transport
* MySQL / Postgres plugins (datastore, datacache) [Radhika]
* UPNP [Milan]
Urgent items (before announcing ng.gnunet.org):
-* TEST:
- - topology (needs TESTING)
- - hostlist (maybe easier with TESTING?)
* 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???)
+ - 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
+ - (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 (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
+ need to bound queueing of replies for other peers
- test multi-peer search/download
* new webpage
- - prevent?
- - migrate Mantis!?
- 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
0.9.0pre0:
* UTIL:
- - heap: "remove_node" can hardly be O(1) given the API, but it should be (!)
- 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!)
+* STATISTICS:
+ - synchronous/asynchronous API (& implementation) is not nice
+ - 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!]
+* 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