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-04 13:55:15 +02:00
parent ccafdc5cd3
commit 656efc7d4e
1 changed files with 7 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

16
TODO.md
View file

@ -6,30 +6,28 @@
and maybe run scripts should be adjusted and maybe run scripts should be adjusted
## aquatic_http ## aquatic_http
* use Either with peer addr, or key if it was sent, as part of peer map key?
Another option would be to generate unique trackerid, send it back and
demand that it's set (make it part of the peer map key), but I don't know
if it is supported in all clients.
* 'left' optional in magnet requests? Probably not. Transmission sends huge
positive number.
* test with real clients * test with real clients
* test tls * test tls
* current serialized byte strings valid? need to test torrent transfer to * current serialized byte strings valid? need to test torrent transfer to
find out find out
* request parsing in protocol module instead of in network, maybe from byte
buffer? Not obvious what error return type to use then (anyhow maybe?)
* scrape: does it work with multiple hashes? * scrape: does it work with multiple hashes?
* StreamEnded isn't really an error and should really only be debug-logged
* non-compact peers for ipv6 generally: use ResponsePeerList enum * non-compact peers for ipv6 generally: use ResponsePeerList enum
* on ipv6, compact=1 should result in error response * on ipv6, compact=1 should result in error response
* on ipv4, compact=0 should result in error response * on ipv4, compact=0 should result in error response
* what does supportcrypto key do? Request upgrade to TLS? * what does supportcrypto key do? Request upgrade to TLS?
* StreamEnded isn't really an error and should really only be debug-logged
### less important
* request parsing in protocol module instead of in network, maybe from byte
buffer? Not obvious what error return type to use then (anyhow maybe?)
* 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
* move stuff to common crate with ws? * move stuff to common crate with ws?
* serialization for future load tester: write custom non-serde serializer * serialization for future load tester: write custom non-serde serializer
for url encode support maybe, or possibly existing crates handle byte for url encode support maybe, or possibly existing crates handle byte
serialization well (then there would still be the question of multiple serialization well (then there would still be the question of multiple
values per key for scrape requests) values per key for scrape requests)
* 'left' optional in magnet requests? Probably not. Transmission sends huge
positive number.
## 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