-0.9.0pre1:
-* FS: [CG]
- - code review:
- => address pbuf sprintf'ing
- - SKS update searches should be attached to individual search results, not to the
- entire SKS search (!)
- => API change (event signalling) & serialization change (!)
- => update search results should be stored in different result directory due
- to possibility of naming conflicts!
- => outch: ditto for recursive downloads (!)
- - persistence testing (publish, unindex, search, download):
- => need driver!
- => schedule suspending tasks DURING event handler => good coverage!
- => test SUSPEND events
- - 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!
-* MIGRATION [CG]
- - on-demand encoding => move logic to block-library!?
- - peer selection => how to consider latency/bw/etc?
- - content transmission => how often the same block?
- - how to select delay before next migration?
- - migration to us
- - testing
- - integrate with FS or not? (peer list, index/on-demand encoding, block code,
- inbound priority assignment; all would be easier with tight integration!)
-* TBENCH: [MW]
- - good to have for transport/DV evaluation!
-* DV: [Nate]
- - write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
- - implement DV service
- - implement DV library (looks done)
- - implement DV transport plugin
- - implement testcases
- - implement performance tests (needs tbench)
-* TOPOLOGY:
- - needs more testing (especially F2F topology) & transport blacklisting
-* UTIL:
- - only connect() sockets that are ready (select()) [Nils]
- [On W32, we need to select after calling socket before doing connect etc.]
-* 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 "gtk_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"?
-* SETUP:
- - design & implement new setup tool
-
-0.9.0pre2:
-* TRACEKIT: [MW]
- - good to have for DV/DHT evaluation!
-* DHT: [Nate]
- - implement DHT service
- - 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)
- - location URIs (publish, search, download)
- - utilize in-line files in meta data always (including in search results or
- when download is triggered manually and for probes); currently the data is
- only used when users do a general 'recursive' 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