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

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-07-03 17:59:28 +02:00
parent 15c75579da
commit 60faf2da3f
1 changed files with 5 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

8
TODO.md
View file

@ -12,6 +12,7 @@
what error return type to use then what error return type to use then
* scrape: does it work with multiple hashes? * scrape: does it work with multiple hashes?
* serialization * serialization
* current serialized byte strings valid?
* there is the question of how serialization should be done for 20 byte * there is the question of how serialization should be done for 20 byte
arrays, such as in the scrape response. There, a 20 byte byte string is arrays, such as in the scrape response. There, a 20 byte byte string is
expected. I think the bendy AsString wrapper is what is needed here, but expected. I think the bendy AsString wrapper is what is needed here, but
@ -19,9 +20,10 @@
combine that with future serialization for load tester, where no bencode combine that with future serialization for load tester, where no bencode
should be involved. LIKELY SOLVED! should be involved. LIKELY SOLVED!
* error response for invalid announce request? * error response for invalid announce request?
* compact response peers should be forbidden for ipv6 * non-compact peers for ipv6 generally: use ResponsePeerList enum
* move stuff to common crate with ws: what about Request/InMessage etc? * on ipv6, compact=1 should result in error response
* don't overdo this * on ipv4, compact=0 should result in error response
* move stuff to common crate with ws?
## aquatic_ws ## aquatic_ws
* established connections do not get valid_until updated, I think? * established connections do not get valid_until updated, I think?