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

only subscribe to a topic on the server side when a client is subscribed to that topic #20

Open
AWatk opened this issue Dec 5, 2017 · 2 comments · May be fixed by #37
Open

only subscribe to a topic on the server side when a client is subscribed to that topic #20

AWatk opened this issue Dec 5, 2017 · 2 comments · May be fixed by #37
Assignees
Labels
Milestone

Comments

@AWatk
Copy link
Member

AWatk commented Dec 5, 2017

If a tree falls in a forest and no one is around to hear it, does it make a sound?

No, no it should not.

@AWatk AWatk changed the title only subscribe to topics on the server side when a client is subscribed to that topic only subscribe to a topic on the server side when a client is subscribed to that topic Dec 5, 2017
@AWatk AWatk added this to the rosmct 0.2 milestone Dec 6, 2017
@AWatk AWatk self-assigned this Dec 6, 2017
@AWatk AWatk added the Ros Sys label Jan 11, 2018
@AWatk
Copy link
Member Author

AWatk commented Jan 11, 2018

can tie the roslib subscribe command to the subscribe callback that is passed up to the realtime server?

@codeflight1
Copy link

This issue should be closed because data points should be recorded in the historical database (#13) even if they are not currently subscribed to. Topics that should never be recorded can be configured in the ros-bridge config.

@codeflight1 codeflight1 linked a pull request Mar 18, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants