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