Planning issue for v4 #3938
Description
I've been discussing v4 of the D-Bus interface with @mulkieran and wanted to create an issue tracking some of my proposals.
@mvollmer As you're the main consumer of our D-Bus API, I'm CCing you.
- Remove versioned interfaces and instead rely on creating new methods on the unified Pool/Manager/etc. interface to expose new parameters.
- Remove our custom error handling for methods and properties and instead rely on the correct D-Bus error type to report errors in the engine.
- Revisit the stop pool method and use an object path for identifying the pool while potentially providing a separate method for cleaning up partially constructed pools.
- Revisit units and types for our properties. @mvollmer Your feedback would be particularly helpful here. For example, are string to integer conversions a problem for you or is that generally painless in JS?