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
-* FS (DHT not available)
+* TESTING-TESTBED [Nate]
* SETUP
-* DV (distributed testing not available)
-* TBENCH (distributed testing not available)
-* TRACEKIT (distributed testing not available)
+* DV [Nate]
+* TBENCH
+* TRACEKIT
+* FRAGMENTATION [Ji Lu]
* HTTP transport
-* FRAGMENTATION
* MySQL / Postgres plugins (datastore, datacache)
-* UPNP
+* UPNP [Milan]
+* ARM [Safey]
Urgent items (before announcing ng.gnunet.org):
* FS (basic anonymous FS only)
- - implement FS service
- + 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
- - implement testcases
- + URI API
- + getopt API
- + sharing API
- ~ file-information
- ~ publish (insert, index)
- ~ download
- ~ search
- ~ unindex
- + directory API
-* 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???)
-* TESTING (needed for DV, DHT, Topology)
- - implement library for local testing
- + modify configuration to allow controlling connections for non-local starts
- + CORE service does not start with valid peer ID (all zeros) -- testcase fails!
- + consider changing API for peer-group termination to call continuation when done
- - implement testcases for library
- + get test for basic peer start to work!
- + test basic peer connect
- + test group start
-* TEST:
- - topology (needs TESTING)
- - hostlist (maybe easier with TESTING?)
+ - 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
- - 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
=> Deploy(able) development network
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)
+* 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;
+ => 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!
+* 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
+ download: loc uris
+ search: sblocks, skblocks, loc uris
+ default generation
+ need to settle basic design; do we want to keep guile?
- testing (RC-pre0)
+ + modify configuration to allow controlling connections for non-local starts
+ testbed creation with topology (needs working F2F topology) [Nate]
+ testbed with churn [Nate]
+ implement library for distributed testing [Nate]
- create good Drupal theme for GNUnet
- make a NICE download page and figure out how to
enable developers to publish TGZs nicely
- - port "contact" page; add impressum
+ - port "contact" page
- add content type for "todo" items?
- DNS activation
* Plugins to implement:
* Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
* Allow checking of presence of search results and/or content via command-line tools
(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