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

Service with the same name, but different messaging pattern shall be allowed. #16

Closed
elfenpiff opened this issue Dec 12, 2023 · 0 comments · Fixed by #55
Closed

Service with the same name, but different messaging pattern shall be allowed. #16

elfenpiff opened this issue Dec 12, 2023 · 0 comments · Fixed by #55

Comments

@elfenpiff
Copy link
Contributor

Brief feature description

Currently, when creating/opening a service with an existing name but a different messaging pattern one receives the failure that it either exists or that the messaging pattern does not match.

It would be better if this would be allowed and that a service is uniquely identified by the messaging pattern and the name.

Detailed information

Should be easily implementable, just hash the messaging pattern as well to acquire the services uuid.

elfenpiff added a commit to elfenpiff/iceoryx2 that referenced this issue Dec 24, 2023
elfenpiff added a commit to elfenpiff/iceoryx2 that referenced this issue Dec 25, 2023
elfenpiff added a commit that referenced this issue Dec 27, 2023
…saging-pattern-allowed

[#16] same name different messaging pattern allowed
hydroid7 pushed a commit to hydroid7/iceoryx2 that referenced this issue Dec 28, 2023
hydroid7 pushed a commit to hydroid7/iceoryx2 that referenced this issue Dec 28, 2023
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.

1 participant