-PHASE #2: (Goal: recover basic file-sharing functionality)
-* TESTING (needed for DV, DHT, Topology)
- - implement library for local testing
- - implement testcases for library
- - implement library for distributed testing [Nate]
- - implement testcases for distributed testing [Nate]
+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-TESTBED [Nate]
+* SETUP
+* DV [Nate]
+* TBENCH
+* TRACEKIT
+* FRAGMENTATION [Ji Lu]
+* HTTP transport
+* MySQL / Postgres plugins (datastore, datacache)
+* UPNP [Milan]
+* ARM [Safey]
+
+Urgent items (before announcing ng.gnunet.org):
+* FS (basic anonymous FS only)
+ - 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
+=> Deploy(able) development network
+
+
+0.9.0pre0:
+* UTIL:
+ - 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!