0.9.0pre1:
+* DATASTORE [CG]
+ - move request queuing functionality into the API library
+* MIGRATION [CG]
+ - on-demand encoding => move logic to block-library!?
+ - peer selection => how to consider latency/bw/etc?
+ - content transmission => how often the same block?
+ - how to select delay before next migration?
+ - migration to us
+ - testing
+ - integrate with FS or not? (peer list, index/on-demand encoding, block code,
+ inbound priority assignment; all would be easier with tight integration!)
* FS: [CG]
- - 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)
- [needed for full persistence support...]
- - persistence support (publish, unindex, search, download)
- 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:700]: member 'ConnectedPeer::last_client_replies_woff' is never used
- GAP improvements:
+ active reply route caching design & implementation of service; gap extension!
-* MIGRATION [CG]
- - on-demand encoding => move logic to block-library!?
- - peer selection => how to consider latency/bw/etc?
- - content transmission => how often the same block?
- - how to select delay before next migration?
- - migration to us
- - testing
- - integrate with FS or not? (peer list, index/on-demand encoding, block code,
- inbound priority assignment; all would be easier with tight integration!)
* TBENCH: [MW]
- good to have for transport/DV evaluation!
* DV: [Nate]
* UTIL:
- only connect() sockets that are ready (select()) [Nils]
[On W32, we need to select after calling socket before doing connect etc.]
+ - add support for UNIX domain sockets [CG]
* 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
* 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
+ => need UNIX domain sockets first!
+ - handle gnunet-arm -k in combination with auto-start magic (what is the right thing here?)
* FS: [CG]
- datastore reservation (publishing)
- 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)
- 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.
0.9.0:
* new webpage:
(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: