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

TODO: reorganize

Browse source
This commit is contained in:
Joakim Frostegård 2020-07-21 23:03:00 +02:00
parent f1f708465a
commit edfb8e62c5
1 changed files with 6 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

11
TODO.md
View file

@ -17,24 +17,25 @@
## aquatic_http ## aquatic_http
* upper limit on request read buffer * upper limit on request read buffer
* request parsing: * add tests
* smartstring: maybe use for keys? maybe use less? needs benchmarking * test response serialization (against data known to be good would be nice)
* test with strange/bad inputs, with and without quickcheck * test request parsing with strange/bad inputs, with and without quickcheck
* 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?
* 'left' optional in magnet requests? Probably not. Transmission sends huge * 'left' optional in magnet requests? Probably not. Transmission sends huge
positive number. positive number.
* tests of response serialization (against data known to be good would be nice)
* compact=0 should result in error response * compact=0 should result in error response
* 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?
### less important ### less important
* request parsing:
* smartstring: maybe use for keys? maybe use less? needs benchmarking
* use fastrand instead of rand? (also for ws and udp then I guess because of * use fastrand instead of rand? (also for ws and udp then I guess because of
shared function) shared function)
* use smartstring crate for failure response reason? * use smartstring for failure response reason?
* log more info for all log modes (function location etc)? also for aquatic_ws * log more info for all log modes (function location etc)? also for aquatic_ws
* Support supportcrypto/requirecrypto keys? Official extension according to * Support supportcrypto/requirecrypto keys? Official extension according to
https://wiki.theory.org/index.php/BitTorrentSpecification#Connection_Obfuscation. https://wiki.theory.org/index.php/BitTorrentSpecification#Connection_Obfuscation.