Skip to content

Control plane transport management

Add the ability to control which EVPath/CM network transport that the control plane uses. Enet (reliable UDP) is still the default, but others can be used, including simple "sockets". Also kick up the ENET connection timeout limit to something huge (because it may take a while at scale to make connections, and if there's nobody there, lots of things will die anyway), and change the TestSst* executables to allow us to specify engine parameters on the command line (facility not currently used, but coming soon). This PR also includes some upstream fixes in EVPath.

Merge request reports

Loading