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
Investigate if dbus-rs emits InterfaceChanged signals properly #1377
Projects
Comments
Correction: The signals are InterfacesAdded and InterfacesRemoved. |
I see a little on the client side of dbus-rs maybe, but nothing on the server side to generate these signals. There are some discouraging comments above |
@jbaublitz it's all yours. |
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Even if our objects do not dynamically change interfaces, InterfaceAdded is the signal that should be emitted when an object is added to the set of object available via GetManagedObjects, and vice-versa for InterfaceRemoved.
We discussed using multiple interfaces to indicate a pool gaining or losing capabilities based on its state. In order to work, changing interfaces should (automatically) cause InterfaceChanged events to be generated. We need to verify this is the case before going much further in investigating this as part of our stable API plans.We are not yet in a situation where we need to change interfaces on our objects.The text was updated successfully, but these errors were encountered: