Post #1126136

unsolicited advice for anyone designing new D-Bus APIs: if you think you need optional properties, you're likely wrong. People forget that interfaces in D-Bus are designed to be dynamic and an object path can have as many interfaces as needed. The advice: split your interfaces well and add/remove them on paths, instead. That's also much cleaner and thanks to ObjectManager interface, there is a well-established way for clients to track any changes in interfaces.