How MistServer handles SRT connections in independent child processes

One of MistServer's (an open source media server) core features is the inherent resilience of handling each connection in a separate process. However, this was not possible for SRT connections using libsrt, since it manages its own sockets as an internal resource. Because of this, for years, MistServer's implementation of SRT used a single process for all connections combined: unlike other protocols in the system! The alternatives would be to either fork libsrt (or hope to upstream some pretty drastic changes) or build an entire alternative library from scratch... Or is a there a secret third option..? Spoiler: there is!