-design flow for grabbing pieces from cache/files
-where to store hashes (currently generated in torrent_file_piece_layers; not stored)
-IDEA: abstract out and store in struct torrent
- -easy access
+ -need to find out what block number is
+ -from piece layer map?
+ -each file piece root
+ -easy access
+ -can easily load up blocks
+ -need easy access
-indexed
+ -to what? - HERE
+ -pieces root (of each file)?
+ -blocks?
+ -need hashmap of all blocks?
+ -otherwise, n^2 search
+ -piece layers?
+ -store pieces in hashmap? in struct torrent
+ -want quick access to file
+ -to easily load data
+ -pointer to struct file?
+ -block number?
-current just in const unsigned char **hashes
-struct piece?
-file location
-toggle/has
-request
-piece
+ -integration test vs. qbittorrent
+ -add debug logging
-tests
-watch
-refactor