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]
+* MySQL / Postgres plugins (datastore, datacache)
* UPNP [Milan]
+* ARM [Safey]
Urgent items (before announcing ng.gnunet.org):
-* TESTING (needed for DV, DHT, Topology)
- - implement library for local testing
- + consider changing API for peer-group termination to
- call continuation when done
- - implement testcases for library
- + test basic peer connect
- + test group start
-* TEST:
- - topology (needs TESTING)
- - hostlist (maybe easier with TESTING?)
+* TRANSPORT:
+ - nondeterministic transport testcase failures [Nate]
* 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 currently fails
+ - request connect not working [Christian, need transport first]
+* TOPOLOGY:
+ - needs testing [need transport first]
+* HOSTLIST:
+ - needs testing [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
- also want to do pushing sometimes?)
- + need to bound queueing of replies for other peers
- - test multi-peer search/download
+ - test multi-peer search/download [needs core first]
* 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!)
+ => should 'scheduler' support SIGCHILD explicitly? Always?
+* STATISTICS:
+ - 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!] [Safey]
+* HELLO:
+ - need function to test "equivalency" of HELLOs; use in topology!
* Module features to implement:
- advanced FS API parts
+ namespaces: fundamental namespace API
+ 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
(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
projects / oweals / gnunet.git / blobdiff