adding support for request queueing to datastore API

[oweals/gnunet.git] / TODO

diff --git a/TODO b/TODO
index 9469382ce5f83e6126b6c835b510cd97ae5d90e8..6cd4b7240720f27e4932e0fe59f7981aee6859fb 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,24 +1,16 @@
 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]
-  - resume signalling for search/download must be recursive!
-  - deserialization code (download)
-  - serialization code (download)
-  - linking of downloads to searches (expose opaque struct SearchResult;
-    allow starting download based on search result (new API):
-    => have meta data for instant completion!
-    => have URI
-    => linking of download to search
-    => expose link to search result in download events (including search result's
-       client-info pointer!)
-  - generate SUSPEND events (publish, unindex, search, download)
-  - actually call 'sync' functions (publish, unindex, search, download)
-  - code review:
-    => refactor fs.c to join common code segments!
-    => document directory structure
-    => ensure all files & dirs are cleaned up! (at least during 'clean' runs)
-  - persistence testing (publish, unindex, search, download):
-    => need driver!
-    => schedule suspending tasks DURING event handler => good coverage!
   - 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
@@ -30,15 +22,6 @@
   - [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]
@@ -53,6 +36,7 @@
 * 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
@@ -75,17 +59,15 @@
 * 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
@@ -125,7 +107,10 @@
   - 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: