Seems I'm suffering from severe brain damage, because I can't remember anymore how one of my older developments works: we had updated the dashboard audio node, to send the audio status ( playing, reset, error,empty ) from the client to the server (where it is being displayed as the node status).
However, suppose N users are running N dashboards simultaneously. In one of those dashboards the audio can still be playing, while in another dashboard the audio has already stopped. But there is only a single audio node in the flow, which is serving multiple dashboard instances. Am I correct that our solution only works correctly if a single dashboard is opened? Or am I missing something fundamental ...
Currently I am developing a camera viewer UI widget. When the user presses a 'stop' button, it has no use to keep on pushing images to the dashboard (since they won't be visualised anyway). So I wanted (somehow??) to send the 'stopped' status back to server, and the server-side part of my widget should ignore input messages (containing images) from then on. But there might be multiple dashboards available: one needs to receive the images, and the other one not.
Any suggestions how I could implement this? Do I have to register this somehow per session?