Skip to content
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

Communicate supported encodings for client-side publishing #131

Merged
merged 1 commit into from
Jan 11, 2023

Conversation

achim-k
Copy link
Collaborator

@achim-k achim-k commented Jan 10, 2023

Public-Facing Changes

  • Communicate supported encodings for client-side publishing

Description
Corresponding spec PR: foxglove/ws-protocol#326

A client currently has no way in determining which message encodings the server supports for client publishing. This PR adds a field to the serverInfo message which informs clients about supported encodings.

@@ -62,14 +62,16 @@ class FoxgloveBridge : public rclcpp::Node {
if (_useSimTime) {
serverCapabilities.push_back(foxglove::CAPABILITY_TIME);
}
const std::vector<std::string> supportedEncodings = {"cdr"};
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why doesn't this one use a static constant when the other one does?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess because we originally planned to support both cdr and idl. Will change it in the future when we have some time for cleanups

@achim-k achim-k merged commit 069cfa4 into main Jan 11, 2023
@achim-k achim-k deleted the achim/add_supported_encodings branch January 11, 2023 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants