mirror of
https://github.com/warmcat/libwebsockets.git
synced 2025-03-30 00:00:16 +01:00
2cfa260e62
This is a NOP for existing usecases. At the moment the only implemented transport for serialized SS is wsi, it's typically used with Unix Domain Sockets, but it also works over tcp the same. It generalizes the interface between serialized chunks and the transport, separately for client and proxy. The wsi transport is migrated to use the new transport ops structs. It will then be possible to "bring your own transport", so long as it is reliable, and in-order, both for proxy and client / sspc. We also adapt minimal-secure-streams-binance to build the -client variant via SS proxy as well. LWS_ONLY_SSPC is added so libwebsockets can be produced with just sspc client support even for tiny targets. A new embedded minimal example for rpi pico is also provided that demonstrates using Serialized SS over a UART to an SS proxy, to implement the SS Binance example on the pico, even though it has no networking itself. |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| minimal-secure-streams.c | ||
| README.md | ||
lws minimal secure streams stress
This is the same as minimal-secure-streams, except you can have it perform concurrent SS connections and a budget of sequential connections.
It basically forks as many times as -c <concurrent> and each fork does --budget <count>
SS connections one after the other.
build
$ cmake . && make
usage
| Commandline option | Meaning |
|---|---|
| -d | Debug verbosity in decimal, eg, -d15 |
| -c | Fork this many times on init |
| --budget | Each fork sequentially does this many SS connections (default 1) |
| --pass-limit | By default the pass limit is the budget, but if doing fault injection you can set a lower limit here |