Camp KDE: Geolocation

Posted Apr 17, 2011 9:03 UTC (Sun) by krake (guest, #55996)
In reply to: Camp KDE: Geolocation by jstaniek
Parent article: Camp KDE: Geolocation

But the backend has to be configured, as you said. And if this configuration system is not a standard, then the whoe solution is not a standard.

I don't agree. The only thing you need to have fixed and neutral is the D-Bus API of the service.

As a client you don't care about any choice in the service's implementation. You simply run the service's D-Bus XML introspection file through qdbusxml2cpp and are done.

The service's D-Bus API would have to be serioulsy flawed to require any kind of dependency to be also present on the client side.