mirror of
https://github.com/YGGverse/aquatic.git
synced 2026-03-31 17:55:36 +00:00
Update TODO
This commit is contained in:
parent
e2638ad7e9
commit
501c2a293a
1 changed files with 4 additions and 4 deletions
8
TODO.md
8
TODO.md
|
|
@ -11,10 +11,10 @@
|
|||
* request parsing in protocol module instead of in network? Not obvious
|
||||
what error return type to use then
|
||||
* 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
|
||||
`?info_hash[0]=..&info_hash[1]` and so on, as I understand it. I guess I
|
||||
could preprocess the query string, but that's kind of ugly, just like the
|
||||
current preprocessing for info_hash and peer_id
|
||||
my own url encode crate. https://github.com/samscott89/serde_qs could be
|
||||
used with extra preprocessing (`?info_hash[0]=..&info_hash[1]` and so on),
|
||||
but it pulls in lots of dependencies (actix-web etc), and current
|
||||
preprocessing is already ugly.
|
||||
* serialization
|
||||
* 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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue