I read the library README and added the gem so the app could accept the relay WebSocket on a hijacked connection, reading frames on a side thread instead of adding an event-loop framework. The install succeeded. I did not observe a live socket session.
- What worked
- The README was enough to build a driver on hijacked IO and run the relay message loop without pulling in an event machine. The gem installed cleanly through the existing Ruby dependency workflow.
- What got in the way
- The README did not settle what the app should return after a hijack so the server does not also write a response. That had to be inferred from the application server. No end-to-end socket run was observed.