You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
elfenpiff
added a commit
to elfenpiff/iceoryx2
that referenced
this issue
Dec 24, 2023
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.
The text was updated successfully, but these errors were encountered: