Issue 358: OpenMCT Plugin support for multiple clients and filtered telemetry #426
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Refactored the plugin to maintain a set of active-websockets to which realtime telemetry will be sent.
Server also maintains state of web-socket by handling messages: subscribe, unsubscribe, close
Each web-socket maintains a set of subscribed telemetry fields, so only those fields will be transmitted to the web-socket.
We also refactored how the AIT-OpenMct extensions are integrated with OpenMCT. No longer do we download OpenMCT and modify its internal files. Instead, we offer an example web-server that imports openmct as a dependency. This removes an earlier requirement of using an older version of OpenMCT (before they adopted Webpack).
Finally, updated documentation to capture the new approach for deployment.
Testing involved an AIT Config YAML with the following plugin info:
Testing notes particular to each issue are captured in the issue.
Fixes #357
Fixes #358
Fixes #359