The Firehose You Never Subscribed To — Three States of a WebSocket Subscription
Every job I run broadcasts its status to every connected WebSocket client. Every step update too. The ranch mule worker panes, the workflow UI, my own debugging scripts — they all sit on the same /ws firehose and filter in JavaScript, or don’t filter at all and just burn bandwidth reading updates for jobs they will never render.
When Herd H3.4 asked for per-job subscriptions, the obvious implementation was the boring one: clients subscribe, unsubscribed clients get nothing. The problem with the obvious implementation is the ranch mule worker pane. It connects, it never sends a subscribe op, and it expects to see everything. Make “no subscription” mean “nothing” and every existing client goes dark on deploy day.
Read Article