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

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-08-17 21:47:08 +02:00
parent 622989e89c
commit 95e8831daf
1 changed files with 9 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

12
TODO.md
View file

@ -5,9 +5,6 @@
of sender if present in selection? maybe make criterion benchmark, of sender if present in selection? maybe make criterion benchmark,
optimize. consider rerunning udp benchmark, last change (filtering out optimize. consider rerunning udp benchmark, last change (filtering out
sender) might have had an adverse impact on performance. sender) might have had an adverse impact on performance.
* automatic tests running real clients in container?
* https://docs.github.com/en/actions/creating-actions/creating-a-docker-container-action
* https://hub.docker.com/_/rust
## aquatic_http_load_test ## aquatic_http_load_test
* how handle large number of peers for "popular" torrents in keepalive mode? * how handle large number of peers for "popular" torrents in keepalive mode?
@ -40,10 +37,19 @@
scrape requests I suppose. scrape requests I suppose.
## aquatic_ws ## aquatic_ws
* websocket_max_frame_size should be at least something like 64 * 1024,
maybe put it and message size at 128k just to be sure
* test transfer again with changes made: * test transfer again with changes made:
* crossbeam-channel * crossbeam-channel
* ipv6/ipv4 mapping * ipv6/ipv4 mapping
* tungstenite 0.11 * tungstenite 0.11
* notes on testing: official tracker does not successfully handle file
transfer on localhost between two instances of the official client
(webtorrent-hybrid), probably due to sdp negotiation issues. so I
shouldn't t pull my hair out trying to figure out why the official
clients won't work with aquatic_ws in this scenario. I should probably
just test manually with clients on multiple machines and skip
automated docker tests
* is 'key' sent in announce request? if so, maybe handle it like in * is 'key' sent in announce request? if so, maybe handle it like in
aquatic_http (including ip uniqueness part of peer map key) aquatic_http (including ip uniqueness part of peer map key)