1 PHASE #1: (Goal: settle key design questions)
4 * API review: should "bpm" and "last_activity" arguments be
5 included in the ClientEventHandler?
7 * Internal: bandwidth allocation (inbound limits, trust)
8 * Internal: advertising (propagate other peers' HELLOs, find new ones)
9 * Internal: bootstrapping
10 => bootstrap should use plugins, possible multiple at the same time!
13 * consider adding "get_time" to "configuration" API
16 For these functions, it would be nice if we had testcases ("make check")
17 that would cause them to be executed and check that they are working:
18 * gnunet-service-peerinfo:
19 - change_host_trust / flush_trust
21 - discard_hosts_helper / cron_clean_data_hosts
22 * gnunet-service-transport:
23 - try_unvalidated_addresses
24 - lookup_address_callback
25 - lookup_hello_callback
26 - plugin_env_lookup_address
27 - notify_clients_disconnect
28 - list_validated_addresses
30 - disconnect_neighbour
32 * plugin_transport_tcp.c:
34 - tcp_plugin_address_pretty_printer / append_port
35 - tcp_plugin_set_receive_quota
38 - GNUNET_TRANSPORT_set_qutoa / send_set_quota
42 - remove_from_any_list / remove_neighbour
43 - GNUNET_TRANSPORT_notify_transmit_ready_cancel
46 - solicit_traffic / copy_and_free
47 - GNUNET_CORE_peer_configure / produce_configure_message
48 * gnunet-service-core:
51 - handle_client_request_configure
54 - handle_transport_notify_disconnect
57 PHASE #2: (Goal: recover basic core functionality)
60 * implement sqlite-based sqstore/datastore service
61 + implement library (talks to service)
62 + implement service (datastore + talks to plugin)
63 + implement sqlite plugin (talks to DB)
64 * implement sqlite-based dstore services
65 + implement library (talks to service)
66 + implement service (talks to plugin)
67 + implement sqlite plugin (talks to DB)
70 * implement hostlist service (need to bootstrap!)
75 * mysql & postgres backend
78 * UDP backend (need LIBRARY to support (de)fragmentation!)
81 + Testcases for set_quota, timeouts, disconnects, transmit_ready_cancel
82 + Better coverage of gnunet-service-transport (hello validation)
83 + direct test of plugins compliance to plugin API
86 PHASE #3: (Goal: ready for pre-release) [completion-goal: end of 2009]
101 - transport_api: support forcing disconnects through low quotas!
102 - API: consider having core provide priority and possibly
103 deadline information for each message
104 (likely important for DV plugin which wants to loop back!)
105 - implement transport API to pretty-print transport address
106 + transport_api extension (API extension!)
107 + service-transport extension (protocol extension)
108 - add calls to statistics in various places
109 - implement gnunet-transport (transport configurator / tester)
110 - UPnP-based IP detection
111 (Note: build library always, build service when libxml2/etc. are available)
112 - instantly filter addresses from *other* peers that
113 are *equal* to our own address + port (i.e., localhost:2086). We
114 no longer filter those for outgoing (helps with loopback testing
115 and keeps the code clean), but we should filter strictly *impossible*
116 incoming addresses! This is for efficiency, not correctness.
117 - We currently are happy to take any address told to us in a WELCOME
118 to our set of addresses; we should have some minimal threshold-based
119 scheme, limiting both the total number of addresses that we accept
120 this way as well as requiring multiple confirmations; also, we
121 should possibly try to confirm that the given address works for
122 us ourselves (loopback-style) before adding it to the list
124 - not sure current way of doing ACKs works well-enough
125 with unreliable transports where the ACK maybe lost;
126 the "is_new" check would then possibly prevent future
127 ACKs to be delivered, all while we're happily
128 receiving messages from that peer! Worse, the other
129 peer won't generate another ACK since it thinks we're
130 connected just fine...
132 + How necessary is ACKing in the first place? (alternatives?)
133 + Should we transmit ACKs in response to every HELLO? (would that
134 fully address the problem?)
135 - latency measurements implemented in the transport
136 plugins makes it only work for bi-di transports
137 and results in code replication
138 - should latency be included in the ReceiveCallback and
139 NotifyConnect or passed on request?
141 - auto-generate "defaults.conf" using gnunet-setup from "config.scm"
142 - integrate all options into "config.scm"
143 - change config-file writing to exclude options set to default values
145 - implement exponential back-off for service restarts
146 - better tracking of which config changes actually need to cause process restarts by ARM.
147 - have way to specify dependencies between services (to manage ARM restarts better)
149 - have gnunet-peerinfo print actual host addresses again
150 - add option to gnunet-peerinfo to modify trust value
152 - finish postgres implementation; simplify other SQLs using new stats
157 - active reply route caching design & implementation of service,
162 PHASE #4: [completion-goal: mid 2010]
170 * Features eliminated from util:
171 - threading (goal: good riddance!)
172 - complex logging features [ectx-passing, target-kinds] (goal: good riddance!)
173 - complex configuration features [defaults, notifications] (goal: good riddance!)
174 - network traffic monitors (goal: eliminate)
175 - IPC semaphores (goal: d-bus? / eliminate?)
177 - DNS lookup (goal: have async service; issue: still need synchronous resolution in places, current code may not be portable)
178 => code shrunk from 61 files to 34, 22k LOC to 15k LOC, 470k to 330k (with symbols)
179 * New features in util:
181 - service and program boot-strap code
182 * Major changes in util:
183 - more expressive server (replaces selector)
185 - how to integrate scheduler with GTK event loop!
190 * UTIL: 75%, 4914 out of 6463