X-Git-Url: https://git.librecmc.org/?a=blobdiff_plain;f=TODO;h=c3b8aa051f382590243f89742b9300c1845d3e4e;hb=9c0e92ec7637b081d35582adfe775f8be7b1f2a3;hp=a407f90526b328e5552fbdcecf0c2417ee1c24a4;hpb=6776eda81f7712d24b4a54943642cf90af7ee4d8;p=oweals%2Fgnunet.git diff --git a/TODO b/TODO index a407f9052..c3b8aa051 100644 --- a/TODO +++ b/TODO @@ -13,32 +13,18 @@ away), in order in which they will likely be done: * ARM [Safey] Urgent items (before announcing ng.gnunet.org): -* UTIL: - - server/service API change for ARM inetd'ing - (listen as well as support for start with multiple, already - bound & listening sockets!) [Christian] -* TRANSPORT: - - main service not implemented [Nate] - - testcases crash & burn (no surprise) -* CORE: - - outbound message monitoring not supported [Christian] - - test currently fails spectacularly [segv of transport service] - => need transport to work first! - - 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 + + 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 @@ -47,8 +33,14 @@ Urgent items (before announcing ng.gnunet.org): - 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? +* 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 @@ -58,6 +50,10 @@ Urgent items (before announcing ng.gnunet.org): [=> 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 @@ -74,8 +70,8 @@ Urgent items (before announcing ng.gnunet.org): + 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