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

Suggestion2: String vs Time message type #4

Open
mbharatheesha opened this issue Jan 28, 2021 · 1 comment · May be fixed by #8
Open

Suggestion2: String vs Time message type #4

mbharatheesha opened this issue Jan 28, 2021 · 1 comment · May be fixed by #8

Comments

@mbharatheesha
Copy link

I see that the message type selected for the sync event is a string that actually sends out a Time message. I can understand this is for optimization, but due to the underlying message serialization that happens before data is sent over the middleware layer, I think its better to use std_msgs/Time message type rather than string.

@poornimajd
Copy link
Owner

Sure,I will try this out.

This was linked to pull requests Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants