-
Notifications
You must be signed in to change notification settings - Fork 487
Add participant hostname, processname, processId #4993
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
Comments
In the "Current" example shown above, is the In general, QoS values are determined by the user and not by the middleware. So the application can add whichever values are needed. There could be a helper function in OpenDDS libraries to augment the PropertyQosPolicy this way, and even a configuration value that automatically does this to each participant when it's enabled. One caveat is that (at least in the current implementation) because the PropertyQosPolicy was added in the DDS Security spec, OpenDDS needs to be built with DDS Security enabled. Also consider that UserDataQosPolicy has an advantage over PropertyQosPolicy - it's in the core DDS spec so every configuration of every implementation should have it. |
It would bring great value if OpenDDS could add these values like other DDS-Vendors do. |
I'm not following this, but perhaps it's not important for the issue at hand. The data type in OpenDDS for the built-in participant topic matches the one in DDS-XTypes v1.3 Annex D.
I'm not against adding it, and I described how it could work above. |
Here is what other vendors automatically add to the RTI:
Cyclone
FastDDS:
|
Just for clarification, are you seeing these values in the Built-In Topic DataReader in a DDS application or from observing the discovery network messages externally (like in Wireshark or similar)? |
yes in the Built-In Topic, not externally. |
the current built in topics do not publish:
But these values are very important for debugging tools to visualize the current system.
Especially for system integrator companies like us using multiple dds-vendors inside a single system.
Current:
What i would like to have:
The text was updated successfully, but these errors were encountered: