YGGverse/aquatic
1
0
Fork 0
mirror of https://github.com/YGGverse/aquatic.git synced 2026-04-02 18:55:32 +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 15:20:42 +02:00
parent e2638ad7e9
commit 501c2a293a
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
TODO.md
View file

@ -11,10 +11,10 @@
* request parsing in protocol module instead of in network? Not obvious * request parsing in protocol module instead of in network? Not obvious
what error return type to use then what error return type to use then
* scrape info hash parsing: multiple ought to be accepted, might need to roll * scrape info hash parsing: multiple ought to be accepted, might need to roll
my own url encode crate. https://github.com/samscott89/serde_qs would require my own url encode crate. https://github.com/samscott89/serde_qs could be
`?info_hash[0]=..&info_hash[1]` and so on, as I understand it. I guess I used with extra preprocessing (`?info_hash[0]=..&info_hash[1]` and so on),
could preprocess the query string, but that's kind of ugly, just like the but it pulls in lots of dependencies (actix-web etc), and current
current preprocessing for info_hash and peer_id preprocessing is already ugly.
* serialization * serialization
* 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