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
+* MySQL / Postgres plugins (datastore, datacache) [Radhika]
+* UPNP [Milan]
Urgent items (before announcing ng.gnunet.org):
+* UTIL:
+ - provide higher-level convenience API for servers/services that
+ need to send a stream of notifications to clients; instead
+ of having each service queue messages and "send when ready",
+ simply have a way to add a client to the notification set
+ and to 'notify client' or 'notify all clients'
+ (useful for peerinfo (new hellos), transport (our hello; blacklist),
+ core (misc monitoring features), statistics (change notifications)
+ and likely others)
+ - server/service API change for ARM inetd'ing
+ (listen as well as support for start with multiple, already
+ bound & listening sockets!)
+* TRANSPORT:
+ - main service not implemented [Nate]
+ - blacklist not implemented [Christian]
+ - testcases crash & burn (no surprise)
+* CORE:
+ - request disconnect not implemented [Christian]
+ - various notification options not implemented [Christian]
+ - test currently fails spectacularly [segv of transport service]
+ => need transport to work first!
+ - request connect not working [Christian, need transport first]
+* PEERINFO:
+ - make sue we also trigger notifications whenever HELLOs expire
+* TOPOLOGY:
+ - needs testing [need transport first]
+* TESTING:
+ - check that 'GNUNET_TRANSPORT_get_hello' is associated with
+ a cancel request wherever appropriate (other testcases
+ in particular!) [Christian]
+* 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) [need transport first]
* FS (basic anonymous FS only)
- - implement FS service
+ - 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
- - 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
* 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
+ gnunet-service-fs (remove failing on-demand blocks, many other nitpicks/features/optimizations)
+ 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
projects / oweals / gnunet.git / blobdiff