* 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):
-* TEST:
- - topology
- - 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???)
* 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
+ + existing bandwidth-reservation code does not work with FS: don't get
+ DBLOCK size bandwidth for reply for a while => trouble for testcase
+ => need to more aggressively increase bandwidth per connection
+ => need to check that bandwidth is assigned properly to begin with
+ + Even with bandwidth-reservation code restricted, message is not
+ delivered to other core/peer/fs. Why?
+ + Same query is sent to the same peer in rather rapid succession (10x/minute?),
+ should tune code to reduce repetition...
* new webpage
- 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
=> Deploy(able) development network
- 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!)
+* TRANSPORT:
+ - disconnect notifications from TCP not always as nice as we might want
+ them to be (but how can we do this cleanly given that UDP is connectionless?)
+ - TCP not used bi-directionally (especially important also for PONG!)
+ - hostlist testcase shows that (randomly) we jump to an address that
+ seems to be a plugin function *after* the plugin has been unloaded
+ (directly from scheduler); check that *all* plugin tasks are cancelled
+ after plugin is unloaded! (need better testcases for that...)
* STATISTICS:
- - synchronous/asynchronous API (& implementation) is not nice
+ - 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!]
+ [=> 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!
+* TOPOLOGY:
+ - needs more testing (especially F2F topology)
+* CORE:
+ - needs more testing
* 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