MultiChannel Atlasboard

I would like to suggest the following enhancements:

Allow a dashboard to show different content based on a the channel it subscribe to As a use case, consider dashboards for a (large) set of users/projects/stocks/customers each presenting different information depending on the identity of the user, project, stock customer etc. - it would be nice to use the same dashboard, same jobs and same widgets - making only the delivered content depend on the identity of the user, project, stock customer being monitored. - at the same opportunity make sure that a dashboard do not get information sent to other dashboards (stop broadcasting to all clients all content)
Have jobs dynamically Start and Stop their activity based on relevant dashboards being active or not. This Start/Stop mechanism informs the Job about channels such that the job would be able to acquire the appropriate channel data and sent it to the listening wizards.

I have created a patch that does that (8 files changed, 80 insertions(+), 29 deletions(-) without testing). It is using Socket.io rooms to achieve the necessery data channeling (item 1 above), and adds onStart() and onStop() for jobs.

For backwards compatibility, if a job does not support the new function, it simply sends data to all dashboards (as done today) using a fixed default channel. This should allow all existing jobs (and all jobs written using the existing spec) to work same as today. Wizards are not affected by this change.

if this is of interest, I can create a pull request and would need assistance in getting the tests in order + creating the assets/build in order (could not find documentation how to do that).

Comments (9)