1 PHASE #1: (Goal: settle key design questions)
4 * hostlist server (MHD-side)
5 * hostlist client (CURL-side); monitoring of number of active connections (to establish need for bootstrapping)
6 * hostlist server URL advertising & learning via P2P
9 * Selecting peers from peerinfo for connects; blacklisting
10 * Managing connections, F2F configuration obedience, rejecting prohibited connections
11 * Forwarding of known HELLOs to neighbours (advertising)
12 [ Inbound HELLOs are processed by transport, right?
13 But what about inbound encrypted HELLOs? ]
16 * Make sure ARM supports daemons (non-service background processes, see hostlist/topology)
19 * improve disk API [Nils]
20 * Windows: use events instead of pipes to signal select()s [Nils]
21 * only connect() sockets that are ready (select())
22 * crypto_hash: use libgcrypt (supports SHA-512 since 2003)
25 For these functions, it would be nice if we had testcases ("make check")
26 that would cause them to be executed and check that they are working:
27 * gnunet-service-peerinfo:
28 - change_host_trust / flush_trust
30 - discard_hosts_helper / cron_clean_data_hosts
31 * gnunet-service-transport:
32 - try_unvalidated_addresses
33 - lookup_address_callback
34 - lookup_hello_callback
35 - plugin_env_lookup_address
36 - notify_clients_disconnect
37 - list_validated_addresses
39 - disconnect_neighbour
41 * plugin_transport_tcp.c:
43 - tcp_plugin_address_pretty_printer / append_port
44 - tcp_plugin_set_receive_quota
47 - GNUNET_TRANSPORT_set_qutoa / send_set_quota
51 - remove_from_any_list / remove_neighbour
52 - GNUNET_TRANSPORT_notify_transmit_ready_cancel
55 - solicit_traffic / copy_and_free
56 - GNUNET_CORE_peer_configure / produce_configure_message
57 * gnunet-service-core:
60 - handle_client_request_configure
63 - handle_transport_notify_disconnect
66 PHASE #2: (Goal: recover basic file-sharing functionality)
69 * implement sqlite-based sqstore/datastore service
70 + implement library (talks to service)
71 + implement service (datastore + talks to plugin)
72 + implement sqlite plugin (talks to DB)
73 * implement sqlite-based dstore services
74 + implement library (talks to service)
75 + implement service (talks to plugin)
76 + implement sqlite plugin (talks to DB)
79 * implement hostlist service (need to bootstrap!)
84 * have ONE backend working
87 PHASE #3: (Goal: ready for pre-release) [completion-goal: end of 2009]
97 * UDP backend (need LIBRARY to support (de)fragmentation!)
100 + Testcases for set_quota, timeouts, disconnects, transmit_ready_cancel
101 + Better coverage of gnunet-service-transport (hello validation)
102 + direct test of plugins compliance to plugin API
105 * sqlite, mysql & postgres backend
111 - inefficient memmove
113 - transport_api: support forcing disconnects through low quotas!
114 - API: consider having core provide deadline information for each message
115 (likely important for DV plugin which wants to loop back!)
116 - implement transport API to pretty-print transport address
117 + transport_api extension (API extension!)
118 + service-transport extension (protocol extension)
119 - add calls to statistics in various places
120 - implement gnunet-transport (transport configurator / tester)
121 - UPnP-based IP detection
122 (Note: build library always, build service when libxml2/etc. are available)
123 - instantly filter addresses from *other* peers that
124 are *equal* to our own address + port (i.e., localhost:2086). We
125 no longer filter those for outgoing (helps with loopback testing
126 and keeps the code clean), but we should filter strictly *impossible*
127 incoming addresses! This is for efficiency, not correctness.
128 - We currently are happy to take any address told to us in a WELCOME
129 to our set of addresses; we should have some minimal threshold-based
130 scheme, limiting both the total number of addresses that we accept
131 this way as well as requiring multiple confirmations; also, we
132 should possibly try to confirm that the given address works for
133 us ourselves (loopback-style) before adding it to the list
135 - not sure current way of doing ACKs works well-enough
136 with unreliable transports where the ACK maybe lost;
137 the "is_new" check would then possibly prevent future
138 ACKs to be delivered, all while we're happily
139 receiving messages from that peer! Worse, the other
140 peer won't generate another ACK since it thinks we're
141 connected just fine...
143 + How necessary is ACKing in the first place? (alternatives?)
144 + Should we transmit ACKs in response to every HELLO? (would that
145 fully address the problem?)
146 - latency measurements implemented in the transport
147 plugins makes it only work for bi-di transports
148 and results in code replication
149 - should latency be included in the ReceiveCallback and
150 NotifyConnect or passed on request?
152 - auto-generate "defaults.conf" using gnunet-setup from "config.scm"
153 - integrate all options into "config.scm"
154 - change config-file writing to exclude options set to default values
156 - implement exponential back-off for service restarts
157 - better tracking of which config changes actually need to cause process restarts by ARM.
158 - have way to specify dependencies between services (to manage ARM restarts better)
160 - have gnunet-peerinfo print actual host addresses again
161 - add option to gnunet-peerinfo to modify trust value
163 - finish postgres implementation; simplify other SQLs using new stats
168 - active reply route caching design & implementation of service,
173 PHASE #4: [completion-goal: mid 2010]
181 * Features eliminated from util:
182 - threading (goal: good riddance!)
183 - complex logging features [ectx-passing, target-kinds] (goal: good riddance!)
184 - complex configuration features [defaults, notifications] (goal: good riddance!)
185 - network traffic monitors (goal: eliminate)
186 - IPC semaphores (goal: d-bus? / eliminate?)
188 - DNS lookup (goal: have async service; issue: still need synchronous resolution in places, current code may not be portable)
189 => code shrunk from 61 files to 34, 22k LOC to 15k LOC, 470k to 330k (with symbols)
190 * New features in util:
192 - service and program boot-strap code
193 * Major changes in util:
194 - more expressive server (replaces selector)
196 - how to integrate scheduler with GTK event loop!
201 * UTIL: 75%, 4914 out of 6463