0.9.0pre1:
-* PEERINFO: [CG]
- - trust: need *fast* way to check/update trust in peers
- (async peerinfo would not be right; certainly not with the current API)
-* TOPOLOGY: [CG]
- - 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 'greylist_after_attempt' being set to 1h,
- which is rather long -- and should probably be adjusted based on
- the number of connections / known peers & use some form of back-off)
- - 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).
- - needs more testing (especially F2F topology)
* FS: [CG]
- - support recursive download even if filename is NULL and we hence
- do not generate files on disk (use temp_filename)
- - bound parallelism (# fs downloads)
- - distinguish in performance tracking and event signalling between
- downloads that are actually running and those that are merely in the queue
- - persistence support (publish, unindex, search, download)
- - active migration support (in fs or in datastore or new daemon?)
- - gnunet-service-fs (hot-path routing, load-based routing, nitpicks)
- - [gnunet-service-fs.c:208]: member 'LocalGetContext::results_bf_size' is never used
- - [gnunet-service-fs.c:501]: member 'PendingRequest::used_pids_size' is never used
- - [gnunet-service-fs.c:654]: member 'ConnectedPeer::last_client_replies' is never used
- - [gnunet-service-fs.c:669]: member 'ConnectedPeer::avg_delay' is never used
- - [gnunet-service-fs.c:675]: member 'ConnectedPeer::avg_priority' is never used
- - [gnunet-service-fs.c:688]: member 'ConnectedPeer::pending_requests' is never used
- - [gnunet-service-fs.c:694]: member 'ConnectedPeer::last_p2p_replies_woff' is never used
- - [gnunet-service-fs.c:700]: member 'ConnectedPeer::last_client_replies_woff' is never used
- - GAP improvements:
- + active reply route caching design & implementation of service; gap extension!
-* TBENCH: [MW]
- - good to have for transport/DV evaluation!
+ - TTL/priority calculations
+ - hot-path routing
+* TRANSPORT:
+ - HTTP backend [MW]
* DV: [Nate]
- write DV API (need to move declarations from dv_api.c to gnunet_dv_service.h!)
- implement DV service
- implement DV library (looks done)
- implement DV transport plugin
- implement testcases
- - implement performance tests
+ - implement performance tests (needs tbench)
* 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
- - use g_main_context_pending, g_main_context_query / g_main_context_check / g_main_context_dispatch
- and NEVER g_main_loop_run (can this be done? might be the clean way to do this! But how
- to integrate this with "gtk_main"? Docu says:
- "It's OK to use the GLib main loop directly instead of gtk_main(), though it involves
- slightly more typing. See GMainLoop in the GLib documentation."
- => so maybe it "just works"?
-* SETUP:
- - design & implement new setup tool
+ - directory support:
+ + download start: recursive/directory (!) & from-URI only
+ + handle download lost-parent (move to 'from-URI only' tab)
+ + display content of directory
+ + open directory
0.9.0pre2:
-* TRACEKIT: [MW]
- - good to have for DV/DHT evaluation!
+* CORE:
+ - transport-level disconnect (i.e. TCP) does not cause core-level
+ disconnect in a timely fashion (waits for connection timeout);
+ need to figure a way to make it near-instant in those cases
+ (i.e. rapid reduction in timeout on transport-level disconnect)
+ - encrypted P2P transmission (loopback) tops at 2 MB/s on my quad-core;
+ why is it so slow? Fix! (see core_api_reliability test)
+ - implement API to get notifications about bandwidth assignments to individual peers
+ - implement API to get notifications about updates to liveness of individual peers (before disconnect)
+* TOPOLOGY:
+ - needs more testing (especially F2F topology) & transport blacklisting
+* TBENCH: [MW]
+ - good to have for transport/DV evaluation!
* DHT: [Nate]
- implement DHT service
- implement testcases
- implement performance tests
-* TRANSPORT:
- - HTTP backend [MW]
* ARM: [Safey]
- - need to get rid of synchronous API for service starts (cause all kinds of problems)
- [=> eliminate for need to tell ARM about service starts most of the time!] [Safey]
- - better tracking of which config changes actually need to cause process restarts by ARM.
- - listen for requests to discover dependencies between services (and avoid
- having to explicitly program start requests)
- better crash management (attach debugging support, capture and analyze
debug output, detect random vs. deterministic crashes)
- - shutdown sequence?
+ - discover dependencies between services
+ - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
+ - add listen socket forwarding to child processes on supported platforms
* FS: [CG]
+ - load considerations (migration, routing)
+ - active reply route caching design & implementation of service; gap extension!
- datastore reservation (publishing)
- - search: availability probes
- location URIs (publish, search, download)
+ - unindex on index failure
+ - utilize in-line files in meta data always (including in search results or
+ when download is triggered manually and for probes); currently the data is
+ only used when users do a general 'recursive' download
- non-anonymous FS service (needs DHT)
+ DHT integration for search
+ CS-DHT-functions (DHT-put of LOC)
+ P2P-functions (DHT-get)
+ - listing of learned namespaces
- collection API & tests
+ gnunet-pseudonym (collection support)
- implement FS performance tests
+ download
+ search
+ unindex
+* STATISTICS:
+ - implement notification-based statistics API
+* GNUNET-GTK:
+ - implement publish dialog details:
+ + open (import directory structure)
+ + normalize keywords (edit subdialog)
+ + set/view previews (edit subdialog)
+ + mark 'insert file' button inconsistent for directories (edit subdialog)
+ - right-clicking on search result should open menu that allows:
+ + starting recursive download
+ + aborting active download
+ + copy URI to clipboard
+ + save-as gnunet-directory
+ - events:
+ + search resume
+ + search error
+ + download error
+ + download resume
+ + publish resume
+ + publish error
+ - implement open directory dialog
+ - implement new-pseudonym dialog
+ - namespace search
+ - NS list in search dialog should use colors to offset our own namespaces from the others
+ - double-clicking on NS list in search dialog should move 'root' to keyword line
+ - right-clicking on NS list in search dialog should open menu that allows
+ + viewing full meta data
+ + deletion of namespace info
+ - extend peer dialog with green-yellow-red connectivity status lights
+ - extend peer dialog with country flags and names
+ - implement statistics tabs
+ - do meaningful update to status line (starting up, peer running, #connections, shutdown, ...)
+ - implement unindex operation (use dialog with all indexed files for selection)
+ - implement download by URI dialog; figure out where to display those downloads!
+ - figure out where in the GUI we should show active uploads/unindex operations and allow aborts
0.9.0pre3:
+* TRACEKIT: [MW]
+ - good to have for DV/DHT evaluation!
* Determine RC bugs and fix those!
+* DATASTORE:
+ - GNUNET_DATASTORE_cancel method not tested
* TESTING: [Nate]
- modify configuration to allow controlling connections for non-local starts
- testbed creation with topology (needs working F2F topology)
* MYSQL database backends: [CG]
- datacache
- datastore
+* FS:
+ - reconstruct IBLOCKS from DBLOCKS if possible (during download; see FIXME in fs_download)
+ - add support for pushing "already seen" search results to FS service for bloomfilter (can wait)
+ - use different 'priority' for probe downloads vs. normal downloads
+* ARM:
+ - better tracking of which config changes actually need to cause process restarts by ARM.
+* SETUP:
+ - design & implement new setup tool
0.9.0:
* new webpage:
- - expand bibliography
- convert documentation pages to books
- update books (especially for developers)
- create good Drupal theme for GNUnet
- - make a NICE download page and figure out how to
- enable developers to publish TGZs nicely
+ - make a NICE download page and figure out how to enable developers to publish TGZs nicely
- port "contact" page
- add content type for "todo" items?
* POSTGRES database backends: [CG]
(Note: build library always, build service when libxml2/etc. are available)
* FS: [CG]
- Remove KBlocks in gnunet-unindex (see discussion with Kenneth Almquist on gnunet-devs in 9/2009)
- - Allow checking of presence of search results and/or content via command-line tools
- (add options to gnunet-search / gnunet-download to limit search to local peer)
* PEERINFO: [CG]
- expire 'ancient' HELLOs (those without valid addresses AND that
we have not 'used' (for their public keys) in a while; need a way
- should use BIO instead of mmap
* TRANSPORT:
- need to periodically probe latency/transport cost changes & possibly switch transport
- - instantly filter addresses from *other* peers that
- are *equal* to our own address + port (i.e., localhost:2086). We
- no longer filter those for outgoing (helps with loopback testing
- and keeps the code clean), but we should filter strictly *impossible*
- incoming addresses! This is for efficiency, not correctness.
- - 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)
+ - should use hash map to look up Neighbours (service AND plugins!)
* DATASTORE (?):
- check for duplicates on insertion (currently, same content is frequently
stored again [seen with KBLOCKS and SBLOCKS]!)
+* PEERINFO:
+ - merge multiple HELLOs of the same peer in the transmission queue
+ (theoretically reduces overhead; bounds message queue size)
+ - merge multiple iteration requests over "all" peers in the queue
+ (theoretically reduces overhead; bounds messgae queue size)
+* FS:
+ - use different queue prioritization for probe-downloads vs. normal downloads (!?)
Minor features:
* TCP:
- [./transport/plugin_transport_tcp.c:391]: (style) struct or union member 'Plugin::address_update_task' is never used (related to issue above)
* TRANSPORT:
- [./transport/gnunet-service-transport.c:173]: (style) struct or union member 'TransportPlugin::rebuild' is never used (related to TCP not refreshing external addresses?)
-* DATACACHE:
- - add stats (# bytes available, # bytes used, # PUTs, # GETs, # GETs satisfied)
-* FS:
- - support inline data in directories for recursive file downloads (fs_download)
-
+* BLOCKS:
+ - testcase would be nice...