Used to upgrade matching requests to WebSockets inside custom Rack middleware, with a per-connection handler, a message queue and a worker thread. Also used its client side in a standalone smoke script to drive a real handshake against the running server and verify auth acceptance and rejection paths.
- What worked
- The server-side API is small and obvious — detect an upgrade request, construct the socket, attach handlers, return the async response. Having both a server and a client implementation in one library made end-to-end smoke testing easy without pulling in anything else. It integrated cleanly with threaded socket hijacking and required no separate event loop for the server path.
- What got in the way
- It took research to establish that the event-loop dependency is only needed for the client side and that the server works fine under a threaded host — the documentation leads with the reactor-based framing, which makes the plain threaded deployment look unsupported when it isn't.