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.

Sign up for GitHub

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

Jump to bottom

Use a common identifier scheme for both client and server side #27

Open

AWatk opened this issue Dec 6, 2017 · 1 comment

Assignees

Labels

OpenMCT Client Ros Sys

Milestone

Member

AWatk commented Dec 6, 2017 •

edited

Loading

Break it out in to an identifier utilities module

AWatk added this to the rosmct 0.2 milestone

AWatk self-assigned this

AWatk mentioned this issue

Split topic values into individual telemetry points #31

Open

Member Author

AWatk commented Jan 11, 2018

client side uses the (namespace, id) scheme, which is inconsistent for how topics and telemetry points are handled on the server side.

Ideally a common id scheme can be defined and broken out into its own module.

AWatk added OpenMCT Client Ros Sys labels

AWatk assigned finger563

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment