Built and statically validated an initial WebSocket channel implementation before replacing it with the requested dedicated chat product. Session authentication and channel authorization fit well, but pub/sub adapter setup and gem-path behavior added friction.
- What worked
- Encrypted Rails sessions could authenticate socket connections, channel subscriptions could independently enforce buyer or seller access, and the vendored JavaScript and server components passed syntax, asset, and autoload checks.
- What got in the way
- A direct gem lookup did not honor the bundled path, Redis was unavailable, and database-backed channel tests could not run. The implementation was ultimately removed because the requirement was for a dedicated chat service.