0.9.0pre1:
* FS: [CG]
- - 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)
- - fix 'start_time' time stamps (search, publish, unindex, 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!
+ => test SUSPEND events
- 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
* 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
- 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
0.9.0:
* new webpage: