0.9.0pre1:
-* PEERINFO:
+* PEERINFO: [CG]
- trust: need *fast* way to check/update trust in peers
(async peerinfo would not be right; certainly not with the current API)
-* STATISTICS:
- - does not seem to work with timeouts (especially if service is not running)
-* UTIL:
- - only connect() sockets that are ready (select()) [Nils]
- [On W32, we need to select after calling socket before doing connect etc.]
-* TOPOLOGY:
- - needs more testing (especially F2F topology)
- - needs to re-try connecting after disconnect (currently, it
- initially triggers a connection request, but if that connection
- fails / goes down, it does not retry in a timely fashion;
- cause seems to be the 'blacklist_after_attempt' being set to 1h,
- which is rather long -- and should probably be adjusted based on
- the number of connections / known peers)
- - If the topology daemon crashes, peers that were put on the
- blacklist with transport will never be removed from it (until
- transport service dies); we should use the blacklist notification
- API to learn about the exact set of blacklisted peers at all times
- (FIXME: the transport_api implementation of blacklisting
- also does not work nicely for this since it won't let us know about
- disconnect-reconnect events and the implicit whitelisting
- that might happen here; that's not so bad since we will
- re-blacklist on pre-connect attempts anyway, so this is
- a minor issue; OTOH, we might want to be more explicit about
- allowing/forbidding connects on pre-connect to avoid
- entering connect attempts to just be blacklisted shortly afterwards).
- - the code uses the term 'blacklist' for both peers that are forbidden
- to connect (i.e. F2F mode) as well as peers that we currently
- won't try to actively connect to ourselves (since we just tried);
- This is confusing. We need two distinct terms (greylist?).
- - move code to use hash table instead of linked list
- - instead of periodically discarding blacklisted entries,
- simply add task that is triggered at the right time (earlier free,
- more balanced load)
- - check if new HELLO learned is different from old HELLO
- before resetting entire state!
-* DATASTORE:
- - API lacks cancellation methods (needed? or is disconnect enough?)
- - may also want to integrate request queuing here instead of gnunet-service-fs_drq.c
+* TRANSPORT: [CG]
+ - need to implement and test new blacklisting code (server-side only, client API exists)
+* TOPOLOGY: [CG]
+ - needs more testing (especially F2F topology) -- need transport blacklisting to be implemented first!
* FS: [CG]
- support recursive download even if filename is NULL and we hence
do not generate files on disk (use temp_filename)
- implement DV transport plugin
- implement testcases
- implement performance tests
+* 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
Optimizations:
* TCP:
- should use hash map to look up sessions
-* PEERINFO:
- - api creates many, many short-lived TCP connections; either some
- clients should use the API differently or we need to change the
- API to enable re-use of connections to the service
* STATISTICS:
- should use BIO instead of mmap
* TRANSPORT:
- should use hash map to look up Neighbours
* HOSTLIST:
- 'server' uses 'GNUNET_PEERINFO_iterate', should probably switch to notification API
- (for more instant / up-to-date hostlists at lower cost) [OPTIMIZATION]
+ (for more instant / up-to-date hostlists at lower cost)
* DATASTORE (?):
- check for duplicates on insertion (currently, same content is frequently
stored again [seen with KBLOCKS and SBLOCKS]!)