YGGverse/aquatic
1
0
Fork 0
mirror of https://github.com/YGGverse/aquatic.git synced 2026-03-31 17:55:36 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-07-19 13:27:54 +02:00
parent 2fe42e7235
commit 09d27d5075
1 changed files with 12 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

14
TODO.md
View file

@ -9,13 +9,18 @@
and maybe run scripts should be adjusted and maybe run scripts should be adjusted
## aquatic_http ## aquatic_http
* request parsing: tests of main function and the various helper functions * request parsing:
* tests of main function and the various helper functions
* hashmap needs ddos protecting hash function, or keys could be checked
against list before insertion
* deserialize 20 bytes: possibly rewrite (just check length of underlying
bytes == 20 and then copy them), also maybe remove String from map for
these cases too
* test torrent transfer with real clients * test torrent transfer with real clients
* test tls * test tls
* current serialized byte strings valid * current serialized byte strings valid
* scrape: does it work (serialization etc), and with multiple hashes? * scrape: does it work (serialization etc), and with multiple hashes?
* compact=0 should result in error response * compact=0 should result in error response
* tests of request parsing
* tests of response serialization (against data known to be good would be nice) * tests of response serialization (against data known to be good would be nice)
* Connection.send_response: handle case when all bytes are not written: can * Connection.send_response: handle case when all bytes are not written: can
write actually block here? And what action should be taken then? write actually block here? And what action should be taken then?
@ -43,6 +48,11 @@
back to requirecrypto peers. Doesn't really work according to reference in back to requirecrypto peers. Doesn't really work according to reference in
https://en.wikipedia.org/wiki/BitTorrent_protocol_encryption https://en.wikipedia.org/wiki/BitTorrent_protocol_encryption
### don't do
* request from path: only urldecode peer_id and info_hash: doesn't really
improve performance
## aquatic_ws ## aquatic_ws
* is 'key' sent in announce request? if so, maybe handle it like in * is 'key' sent in announce request? if so, maybe handle it like in
aquatic_http (including ip uniqueness part of peer map key) aquatic_http (including ip uniqueness part of peer map key)