Used it on both sides of the audio path: server-side to accept an upgraded media-stream connection inside a Rack app, and client-side over a TLS socket to talk to a streaming transcription service. Verified that a non-upgrade request is correctly rejected so the app falls through to a normal response; no live socket session was exercised.
- What worked
- It is protocol-only and transport-agnostic, which is exactly right for embedding in an existing Rack process and for driving a raw TLS socket. Detecting whether a request is an upgrade attempt is a single clean call. Being already present transitively meant no new heavyweight dependency.
- What got in the way
- Using it as a client requires hand-writing a small socket adapter and your own read pump, plus wiring custom handshake headers and query parameters yourself. The low-level design is defensible but the documentation assumes you already know that shape, so getting from zero to a working client is more guesswork than it should be.