From e2638ad7e917ef789385f4a754f8ca7f6a08955c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20Frosteg=C3=A5rd?= Date: Fri, 3 Jul 2020 14:42:18 +0200 Subject: [PATCH] Update TODO --- TODO.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/TODO.md b/TODO.md index 9b2e45a..879a880 100644 --- a/TODO.md +++ b/TODO.md @@ -11,7 +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 anyway or possibly use https://github.com/samscott89/serde_qs + 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 * 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