Merge pull request #5258 from IntersectMBO/mw/bootstrap-timeout
Respect bootstrap peers timeout
Respect bootstrap peers timeout
Allows to reset the timeouts
The client sends an initial request, the server responds with a number of replies, then the server terminates the protocol. The original design had the problem that the Leios traffic was sending data while the Praos was making another request (around 10 full MuxSDUs), and since Praos is making more requests than Leios, it skews the results. TODO: the client should send how many replies to get, then the commands to run this version would be similar to the original.
* leios block is 1000 MuxSDUs * praos block is 10 MuxSDUs Define `EGRESS_THROUPUT`, `INGRESS_DELAY` and `RTS_OPTIONS` for easier configuration.
Sync with next MuxSDU if a tcp packet was lost.
This script is based on `ouroboros-consensus` leios demo.
This allows us to run mux-leios-demo without `CBOR` encoding.
A mux demo with two mini-protocols, to simulate Praos & Leios traffic which happen simultaneously.
* leios block is 1000 MuxSDUs * praos block is 10 MuxSDUs Define `EGRESS_THROUPUT`, `INGRESS_DELAY` and `RTS_OPTIONS` for easier configuration.
Sync with next MuxSDU if a tcp packet was lost.
The client sends an initial request, the server responds with a number of replies, then the server terminates the protocol. The original design had the problem that the Leios traffic was sending data while the Praos was making another request (around 10 full MuxSDUs), and since Praos is making more requests than Leios, it skews the results. TODO: the client should send how many replies to get, then the commands to run this version would be similar to the original.
This allows us to run mux-leios-demo without `CBOR` encoding.
This script is based on `ouroboros-consensus` leios demo.
A mux demo with two mini-protocols, to simulate Praos & Leios traffic which happen simultaneously.
The client sends an initial request, the server responds with a number of replies, then the server terminates the protocol. The original design had the problem that the Leios traffic was sending data while the Praos was making another request (around 10 full MuxSDUs), and since Praos is making more requests than Leios, it skews the results. TODO: the client should send how many replies to get, then the commands to run this version would be similar to the original.