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

Update TODO

Browse source
This commit is contained in:
Joakim Frostegård 2020-07-24 20:33:37 +02:00
parent b1f998830d
commit 3802dec79e
1 changed files with 9 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

10
TODO.md
View file

@ -12,17 +12,25 @@
* 80k responses per second is possible with low poll timeout values. Probably * 80k responses per second is possible with low poll timeout values. Probably
has to do with exact timing of receiving responses and sending requests. has to do with exact timing of receiving responses and sending requests.
I should also try to reduce event capacity.
* think about when to open new connections * think about when to open new connections
* opening new connections in current form causes macOS issues, why? * opening new connections in current form causes macOS issues, why?
* try creating sockets with different ports (and also local ips if setting
enabled), then passing converting them to mio tcp streams
## aquatic_http ## aquatic_http
* upper limit on request read buffer * upper limit on request read buffer
* don't allocate for response serialization, pass reference to cursor over
array instead and write to impl Write in functions instead (same in load
test, there also for urlencode)
* try using crossbeam instead, see if it improves performance
* check if connection ValidUntil's are really updated when necessary. there
are some connections dropped after a while when load testing
* add tests * add tests
* test response serialization (against data known to be good would be nice) * test response serialization (against data known to be good would be nice)
* test request parsing with strange/bad inputs, with and without quickcheck * test request parsing with strange/bad inputs, with and without quickcheck
* test torrent transfer with real clients * test torrent transfer with real clients
* test tls * test tls
* current serialized byte strings valid
* scrape: does it work (serialization etc), and with multiple hashes? * scrape: does it work (serialization etc), and with multiple hashes?
* 'left' optional in magnet requests? Probably not. Transmission sends huge * 'left' optional in magnet requests? Probably not. Transmission sends huge
positive number. positive number.