updated using git-extra

diff --git a/todo b/todo
index 414132c34a744215a20dd27345f2de50a066e977..937121f1acdcd4709f74f07a017e745b0bfd5838 100644 (file)
--- a/todo
+++ b/todo
@@ -17,6 +17,8 @@ Resources:
        -https://doc.libsodium.org/
 
 To Do:
+-setup qbittorrent integration testing
+       -debug peer protocol/piece ambiguity
 -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
@@ -27,11 +29,19 @@ To Do:
                                -can easily load up blocks
                -need easy access
                        -indexed
-                       -to what? - HERE
+                       -to what?
+                               -infohash -> pieces_root -> blocks (this is the index)
+                                       -to find i-th piece
+                                               -sort roots
+                                               -count pieces in each root
+                                               -go i, going to next file as necessary
+                               -create struct with root, # of pieces, can easily sort
+                                       -need root hash in struct?
+                                               -extra space
+                                       -if i>pieces_count, i -= pieces_count, -> next struct
+                                       -then, piece_layers++, i--, blocks++++(as necessary based on ratio)
+                                       -then, load blocks
                                -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