mirror of
https://github.com/YGGverse/aquatic.git
synced 2026-04-02 10:45:30 +00:00
Update TODO
This commit is contained in:
parent
8bf9f2c408
commit
885640a385
1 changed files with 7 additions and 2 deletions
9
TODO.md
9
TODO.md
|
|
@ -1,16 +1,19 @@
|
||||||
# TODO
|
# TODO
|
||||||
|
|
||||||
|
Set default server addresses to 0.0.0.0! (or maybe ipv6 equivalent, which I
|
||||||
|
think is `[::]`). Update README default configs
|
||||||
|
|
||||||
## aquatic_ws
|
## aquatic_ws
|
||||||
* network
|
* network
|
||||||
* test tls with full torrent transfer (offer-answer exchange) and multiple
|
|
||||||
socket workers
|
|
||||||
* handle tls certificate parse errors etc better
|
* handle tls certificate parse errors etc better
|
||||||
* parse once only
|
* parse once only
|
||||||
* exit with error message, not with panic
|
* exit with error message, not with panic
|
||||||
|
* handle socket binding errors better (print them and exit)
|
||||||
* send/recv buffer size config
|
* send/recv buffer size config
|
||||||
* limit ws message sizes?
|
* limit ws message sizes?
|
||||||
* privdrop
|
* privdrop
|
||||||
* config
|
* config
|
||||||
|
* make HandshakeHandler non-public
|
||||||
* some config.network fields are actually used in handler. maybe they should
|
* some config.network fields are actually used in handler. maybe they should
|
||||||
be checked while parsing? not completely clear
|
be checked while parsing? not completely clear
|
||||||
* ipv4 / ipv6 split state?
|
* ipv4 / ipv6 split state?
|
||||||
|
|
@ -21,6 +24,8 @@
|
||||||
* log crate instead of println/eprintln?
|
* log crate instead of println/eprintln?
|
||||||
|
|
||||||
## aquatic_udp
|
## aquatic_udp
|
||||||
|
* if socket workers panic while binding, don't sit around and wait for them
|
||||||
|
in privdrop function. Maybe wait some maximum amount of time?
|
||||||
* mio: set oneshot for epoll and kqueue? otherwise, stop reregistering?
|
* mio: set oneshot for epoll and kqueue? otherwise, stop reregistering?
|
||||||
* Handle Ipv4 and Ipv6 peers. Probably split torrent state. Ipv4 peers
|
* Handle Ipv4 and Ipv6 peers. Probably split torrent state. Ipv4 peers
|
||||||
can't make use of Ipv6 ones. Ipv6 ones may or may note be able to make
|
can't make use of Ipv6 ones. Ipv6 ones may or may note be able to make
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue