mirror of
https://github.com/YGGverse/aquatic.git
synced 2026-03-31 17:55:36 +00:00
TODO: reorganize
This commit is contained in:
parent
f1f708465a
commit
edfb8e62c5
1 changed files with 6 additions and 5 deletions
11
TODO.md
11
TODO.md
|
|
@ -17,24 +17,25 @@
|
|||
|
||||
## aquatic_http
|
||||
* upper limit on request read buffer
|
||||
* request parsing:
|
||||
* smartstring: maybe use for keys? maybe use less? needs benchmarking
|
||||
* test with strange/bad inputs, with and without quickcheck
|
||||
* add tests
|
||||
* test response serialization (against data known to be good would be nice)
|
||||
* test request parsing with strange/bad inputs, with and without quickcheck
|
||||
* test torrent transfer with real clients
|
||||
* test tls
|
||||
* current serialized byte strings valid
|
||||
* scrape: does it work (serialization etc), and with multiple hashes?
|
||||
* 'left' optional in magnet requests? Probably not. Transmission sends huge
|
||||
positive number.
|
||||
* tests of response serialization (against data known to be good would be nice)
|
||||
* compact=0 should result in error response
|
||||
* Connection.send_response: handle case when all bytes are not written: can
|
||||
write actually block here? And what action should be taken then?
|
||||
|
||||
### 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
|
||||
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
|
||||
* Support supportcrypto/requirecrypto keys? Official extension according to
|
||||
https://wiki.theory.org/index.php/BitTorrentSpecification#Connection_Obfuscation.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue