-* CORE:
- - needs more testing
-* Module features to implement:
- - advanced FS API parts
- + namespaces: fundamental namespace API
- + search: SBlocks, KSBlocks, probes, notify FS-service of known results
- + collection
- + location URIs (publish, search, download)
- + persistence support (publish, unindex, search, download)
- + indexing: index-failure-cleanup
- + download: management/bounding of parallel downloads (for recursive dl.)
- + datastore reservation (publishing)
- + gnunet-publish (URI args)
- + gnunet-download (directory)
- + gnunet-search (options, incl. namespace search)
- + gnunet-download (many options)
- + gnunet-directory (man page, options)
- + gnunet-pseudonym (all of it)
- + 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
- + namespaces
- + collection
- - implement FS performance tests (needs TESTING)
+ - needs to re-try connecting after disconnect (currently, it
+ initially triggers a connection request, but if that connection
+ fails / goes down, it does not retry in a timely fashion;
+ cause seems to be the 'blacklist_after_attempt' being set to 1h,
+ which is rather long -- and should probably be adjusted based on
+ the number of connections / known peers)
+ - If the topology daemon crashes, peers that were put on the
+ blacklist with transport will never be removed from it (until
+ transport service dies); we should use the blacklist notification
+ API to learn about the exact set of blacklisted peers at all times
+ (FIXME: the transport_api implementation of blacklisting
+ also does not work nicely for this since it won't let us know about
+ disconnect-reconnect events and the implicit whitelisting
+ that might happen here; that's not so bad since we will
+ re-blacklist on pre-connect attempts anyway, so this is
+ a minor issue; OTOH, we might want to be more explicit about
+ allowing/forbidding connects on pre-connect to avoid
+ entering connect attempts to just be blacklisted shortly afterwards).
+ - the code uses the term 'blacklist' for both peers that are forbidden
+ to connect (i.e. F2F mode) as well as peers that we currently
+ won't try to actively connect to ourselves (since we just tried);
+ This is confusing. We need two distinct terms (greylist?).
+ - move code to use hash table instead of linked list
+ - instead of periodically discarding blacklisted entries,
+ simply add task that is triggered at the right time (earlier free,
+ more balanced load)
+ - check if new HELLO learned is different from old HELLO
+ before resetting entire state!
+* FS: [CG]
+ - support recursive download even if filename is NULL and we hence
+ do not generate files on disk (use temp_filename)
+ - bound parallelism (# fs downloads)
+ - distinguish in performance tracking and event signalling between
+ downloads that are actually running and those that are merely in the queue
+ - persistence support (publish, unindex, search, download)
+ - active migration support (in fs or in datastore or new daemon?)
+ - gnunet-service-fs (hot-path routing, load-based routing, nitpicks)
+ - [gnunet-service-fs.c:208]: member 'LocalGetContext::results_bf_size' is never used
+ - [gnunet-service-fs.c:501]: member 'PendingRequest::used_pids_size' is never used
+ - [gnunet-service-fs.c:654]: member 'ConnectedPeer::last_client_replies' is never used
+ - [gnunet-service-fs.c:669]: member 'ConnectedPeer::avg_delay' is never used
+ - [gnunet-service-fs.c:675]: member 'ConnectedPeer::avg_priority' is never used
+ - [gnunet-service-fs.c:688]: member 'ConnectedPeer::pending_requests' is never used
+ - [gnunet-service-fs.c:694]: member 'ConnectedPeer::last_p2p_replies_woff' is never used
+ - [gnunet-service-fs.c:700]: member 'ConnectedPeer::last_client_replies_woff' is never used
+ - GAP improvements:
+ + active reply route caching design & implementation of service; gap extension!
+* DATASTORE:
+ - API lacks cancellation methods (needed? or is disconnect enough?);
+ may also want to integrate request queuing here instead of gnunet-service-fs_drq.c
+* GNUNET-GTK:
+ - use g_main_context_set_poll_func to integrate GTK with GNUnet Scheduler!? (YUCK!)
+ - OR: add scheduler API to enable integration with GTK main loop instead of doing our own select
+ - use g_main_context_pending, g_main_context_query / g_main_context_check / g_main_context_dispatch
+ and NEVER g_main_loop_run (can this be done? might be the clean way to do this! But how
+ to integrate this with "tak_main"? Docu says:
+ "It's OK to use the GLib main loop directly instead of gtk_main(), though it involves
+ slightly more typing. See GMainLoop in the GLib documentation."
+ => so maybe it "just works"?
+
+0.9.0pre2:
+* TRACEKIT: [MW]
+ - good to have for DV/DHT evaluation!
+* DHT: [Nate]
+ - implement DHT service
+ - implement DHT library
+ - implement testcases
+ - implement performance tests
+* TRANSPORT:
+ - HTTP backend [MW]
+* ARM: [Safey]
+ - 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]
+ - better tracking of which config changes actually need to cause process restarts by ARM.
+ - listen for requests to discover dependencies between services (and avoid
+ having to explicitly program start requests)
+ - better crash management (attach debugging support, capture and analyze
+ debug output, detect random vs. deterministic crashes)
+ - shutdown sequence?
+* FS: [CG]
+ - datastore reservation (publishing)
+ - search: availability probes
+ - location URIs (publish, search, download)
+ - non-anonymous FS service (needs DHT)
+ + DHT integration for search
+ + CS-DHT-functions (DHT-put of LOC)
+ + P2P-functions (DHT-get)
+ - collection API & tests
+ + gnunet-pseudonym (collection support)
+ - implement FS performance tests