3 - generate SUSPEND events (publish, unindex, search, download) AND free memory!
4 - actually call 'sync' functions (publish, unindex, search, download)
5 - linking of downloads to searches (expose opaque struct SearchResult;
6 allow starting download based on search result (new API):
7 => have meta data for instant completion!
9 => linking of download to search
10 => expose link to search result in download events (including search result's
13 => refactor fs.c to join common code segments!
14 => document directory structure (and use #define's for the directory names!)
15 => ensure all files & dirs are cleaned up! (at least during 'clean' runs)
16 - persistence testing (publish, unindex, search, download):
18 => schedule suspending tasks DURING event handler => good coverage!
19 - gnunet-service-fs (hot-path routing, load-based routing, nitpicks)
20 - [gnunet-service-fs.c:208]: member 'LocalGetContext::results_bf_size' is never used
21 - [gnunet-service-fs.c:501]: member 'PendingRequest::used_pids_size' is never used
22 - [gnunet-service-fs.c:654]: member 'ConnectedPeer::last_client_replies' is never used
23 - [gnunet-service-fs.c:669]: member 'ConnectedPeer::avg_delay' is never used
24 - [gnunet-service-fs.c:675]: member 'ConnectedPeer::avg_priority' is never used
25 - [gnunet-service-fs.c:688]: member 'ConnectedPeer::pending_requests' is never used
26 - [gnunet-service-fs.c:694]: member 'ConnectedPeer::last_p2p_replies_woff' is never used
27 - [gnunet-service-fs.c:700]: member 'ConnectedPeer::last_client_replies_woff' is never used
29 + active reply route caching design & implementation of service; gap extension!
31 - on-demand encoding => move logic to block-library!?
32 - peer selection => how to consider latency/bw/etc?
33 - content transmission => how often the same block?
34 - how to select delay before next migration?
37 - integrate with FS or not? (peer list, index/on-demand encoding, block code,
38 inbound priority assignment; all would be easier with tight integration!)
40 - good to have for transport/DV evaluation!
42 - write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
43 - implement DV service
44 - implement DV library (looks done)
45 - implement DV transport plugin
47 - implement performance tests (needs tbench)
49 - needs more testing (especially F2F topology) & transport blacklisting
51 - only connect() sockets that are ready (select()) [Nils]
52 [On W32, we need to select after calling socket before doing connect etc.]
54 - use g_main_context_set_poll_func to integrate GTK with GNUnet Scheduler!? (YUCK!)
55 - OR: add scheduler API to enable integration with GTK main loop instead of doing our own select
56 - use g_main_context_pending, g_main_context_query / g_main_context_check / g_main_context_dispatch
57 and NEVER g_main_loop_run (can this be done? might be the clean way to do this! But how
58 to integrate this with "gtk_main"? Docu says:
59 "It's OK to use the GLib main loop directly instead of gtk_main(), though it involves
60 slightly more typing. See GMainLoop in the GLib documentation."
61 => so maybe it "just works"?
63 - design & implement new setup tool
67 - good to have for DV/DHT evaluation!
69 - implement DHT service
71 - implement performance tests
75 - need to get rid of synchronous API for service starts (cause all kinds of problems)
76 [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
77 - better tracking of which config changes actually need to cause process restarts by ARM.
78 - listen for requests to discover dependencies between services (and avoid
79 having to explicitly program start requests)
80 - better crash management (attach debugging support, capture and analyze
81 debug output, detect random vs. deterministic crashes)
84 - datastore reservation (publishing)
85 - location URIs (publish, search, download)
86 - utilize in-line files in meta data always (including in search results or
87 when download is triggered manually and for probes); currently the data is
88 only used when users do a general 'recursive' download
89 - non-anonymous FS service (needs DHT)
90 + DHT integration for search
91 + CS-DHT-functions (DHT-put of LOC)
92 + P2P-functions (DHT-get)
93 - collection API & tests
94 + gnunet-pseudonym (collection support)
95 - implement FS performance tests
101 - improved content selection (not just 'get_random')
104 * Determine RC bugs and fix those!
106 - modify configuration to allow controlling connections for non-local starts
107 - testbed creation with topology (needs working F2F topology)
109 - implement testcases for distributed testing
110 - test basic peer re-configure
111 - test topology creation
112 - test churn generation
113 - consider changing API for peer-group termination to
114 call continuation when done
116 - finalize API design
119 - integration with transport service
120 * MYSQL database backends: [CG]
124 - reconstruct IBLOCKS from DBLOCKS if possible (during download; see FIXME in fs_download)
129 - expand bibliography
130 - convert documentation pages to books
131 - update books (especially for developers)
132 - create good Drupal theme for GNUnet
133 - make a NICE download page and figure out how to enable developers to publish TGZs nicely
134 - port "contact" page
135 - add content type for "todo" items?
136 * POSTGRES database backends: [CG]
139 * Determine RC bugs and fix those!
143 - SMTP transport backend
144 - HTTPS transport backend
145 + improved HTTPS support in MHD
147 - Implement method of learning our external addresses from
148 other peers; need some kind of threshold-based
149 scheme, limiting both the total number of addresses that we accept
150 this way as well as requiring multiple confirmations; also, we
151 should possibly try to confirm that the given address works for
152 us ourselves (loopback-style) before adding it to the list
153 + we may be able to simplify WELCOME messages (no need to add
154 addresses there anymore, but may help to learn them there anyway...).
155 + we probably want some kind of voting/counting for learning IP addresses
156 (maybe including IP addresses in ads proportional to how often others
157 report them? we at least need some protection against >64k HELLOs!),
158 + provide a way to give the user a list of "learned" IP addresses and
159 a way to easily "veto" addresses off the list!
160 => If MiM attacker uses vetoed address, blacklist the specific IP for
161 the presumed neighbour!
162 - implement gnunet-transport (transport configurator / tester)
163 - UPnP-based IP detection
164 (Note: build library always, build service when libxml2/etc. are available)
166 - Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
168 - expire 'ancient' HELLOs (those without valid addresses AND that
169 we have not 'used' (for their public keys) in a while; need a way
170 to track actual 'use')
171 - make sue we also trigger notifications whenever HELLOs expire
178 - should use hash map to look up sessions
180 - should use BIO instead of mmap
182 - need to periodically probe latency/transport cost changes & possibly switch transport
183 - should use hash map to look up Neighbours (service AND plugins!)
185 - check for duplicates on insertion (currently, same content is frequently
186 stored again [seen with KBLOCKS and SBLOCKS]!)
188 - merge multiple HELLOs of the same peer in the transmission queue
189 (theoretically reduces overhead; bounds message queue size)
190 - merge multiple iteration requests over "all" peers in the queue
191 (theoretically reduces overhead; bounds messgae queue size)
193 - use different queue prioritization for probe-downloads vs. normal downloads (!?)
197 - repeatedly resolve hostname and look up interfaces to determine our own IP
198 - [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
200 - [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
202 - testcase would be nice...