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

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-07-02 21:16:13 +02:00
parent f73910934b
commit 81983b98a2
1 changed files with 7 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

10
TODO.md
View file

@ -7,9 +7,7 @@
## aquatic_http ## aquatic_http
* handshake stuff * handshake stuff
* fix overcomplicated and probably incorrect implementation * fix overcomplicated and possibly incorrect implementation
* support TLS and plain at the same time??
* really close connections after sending response??
* fixed size buffer is probably bad * fixed size buffer is probably bad
* compact peer representation in announce response: is implementation correct? * compact peer representation in announce response: is implementation correct?
* scrape info hash parsing: multiple ought to be accepted * scrape info hash parsing: multiple ought to be accepted
@ -110,6 +108,12 @@ just like best results in last benchmark, multiple client ips=true:
* target-cpu=skylake: 439k * target-cpu=skylake: 439k
* no target-cpu set: 388k * no target-cpu set: 388k
## aquatic_http / aquatic_ws
* Shared state for HTTP with and without TLS. Peers who announce over TLS
should be able to expect that someone snooping on the connection can't
connect them to a info hash. If someone receives their IP in a response
while announcing without TLS, this expectation would be broken.
## aquatic_udp ## aquatic_udp
* Other HashMap hashers (such as SeaHash): seemingly not worthwhile, see * Other HashMap hashers (such as SeaHash): seemingly not worthwhile, see