Pulled in as the reactor underneath the WebSocket layer and used to push blocking model and HTTP calls off the event loop so the connection stayed responsive to interruptions. Installed and loaded cleanly in an isolated bundle alongside the transport libraries.
- What worked
- Installed without native build trouble and gave a straightforward way to move blocking work onto a thread pool with completion and error callbacks, which is exactly what an interruption-sensitive turn loop needs.
- What got in the way
- The deferred-work callback signature is the kind of thing you have to confirm against a specific version rather than recall, and the whole reactor model imposes a web-server choice on the rest of the service. It feels like infrastructure from an earlier era that you adopt because a transport library requires it, not because you chose it.