-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorial updates #17
Tutorial updates #17
Conversation
realtime-telemetry-plugin.js
Outdated
@@ -20,22 +18,11 @@ function RealtimeTelemetryPlugin() { | |||
return domainObject.type === 'example.telemetry'; | |||
}, | |||
subscribe: function (domainObject, callback, options) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@larkin The options argument is no longer needed since the recent changes to the telemetry API doesn't require it.
example-server/realtime-server.js
Outdated
router.ws('/', function (ws) { | ||
var unlisten = spacecraft.listen(notifySubscribers); | ||
subscribed = {}, // Active subscriptions for this connection | ||
handlers = { // Handlers for specific requests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@larkin var is missing at line 9.
@psarram this looks good. When we merge this we also have to update tags for the steps. Can you merge locally, generate new tags, and push new master + new tags together? |
Simplify realtime provider Due to nasa/openmct#1594 we no longer need to worry about multiple calls for the same identifier. Host all routes on same port, use host-relative urls for client Update readme
00df420
to
b1c24b4
Compare
Some updates based on revisions to openmct APIs.