- - implement FS service
- + how to send queries (soliciting is not there in core; do we
- also want to do pushing sometimes?)
- + need to bound queueing of replies for other peers
- - implement testcases
- + URI API
- + getopt API
- + sharing API
- ~ file-information
- ~ publish (insert, index)
- ~ download
- ~ search
- ~ unindex
- + directory API
-* CORE:
- - soliciting traffic for clients that registered for it is not implemented
- (in the service, client API supports GNUNET_MESSAGE_TYPE_CORE_SOLICIT_TRAFFIC
- but never receives any such messages); how to avoid busy-waiting here
- is a good question (solicit => nothing, when to solicit again???)
-* TESTING (needed for DV, DHT, Topology)
- - implement library for local testing
- + modify configuration to allow controlling connections for non-local starts
- + CORE service does not start with valid peer ID (all zeros) -- testcase fails!
- + consider changing API for peer-group termination to call continuation when done
- - implement testcases for library
- + get test for basic peer start to work!
- + test basic peer connect
- + test group start
-* TEST:
- - topology (needs TESTING)
- - hostlist (maybe easier with TESTING?)
+ - test multi-peer search/download
+ + existing bandwidth-reservation code does not work with FS: don't get
+ DBLOCK size bandwidth for reply for a while => trouble for testcase
+ => need to more aggressively increase bandwidth per connection
+ => need to check that bandwidth is assigned properly to begin with
+ + Even with bandwidth-reservation code restricted, message is not
+ delivered to other core/peer/fs. Why?
+ + Same query is sent to the same peer in rather rapid succession (10x/minute?),
+ should tune code to reduce repetition...