ROS1 Services support persistent #213
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
While interacting with zenoh-ros1-bridge I discovered that their implementation or ROS1 service clients (rosrust based) didn't "complete" a service request until the underlying TCP socket shutdown. They relied on a service server closing the TCP socket after the request is completed if the persistent flag was not set in the header. I don't love that they are doing that and filed an issue over there, but we should improve our support for the persistent flag regardless.
eclipse-zenoh/zenoh-plugin-ros1#212
Fixes
Checklist