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

node with the same name #186

Closed
reed-lau opened this issue Aug 21, 2018 · 1 comment
Closed

node with the same name #186

reed-lau opened this issue Aug 21, 2018 · 1 comment
Labels
question Further information is requested

Comments

@reed-lau
Copy link

in ROS2's concept, can it has the node with the same name, expecially considering the builtin client service (eg. list_parameters, get_parameters, set_parameters ...), for this will make the two node fully connected by these services and clients.

@wjwwood
Copy link
Member

wjwwood commented Aug 21, 2018

The current unwritten assumption is that node names need to be unique. There's a long standing task to make a design document on this topic with details on how to enforce the node name uniqueness (given that discovery is by default distributed without a master).

We're talked about it several times off-line, but it's explicitly mentioned as a design issue on this issue about parameter refactoring: ros2/ros2#432

I'll close this for now as it's more of a question, but I made this issue to track the need for the design document about this: #187

@wjwwood wjwwood closed this as completed Aug 21, 2018
@wjwwood wjwwood added the question Further information is requested label Aug 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants