Re: [PATCH 01/13] kdbus: add documentation

[Tom Gundersen <teg@jklm.no>]

Hi Michael,

On Mon, Jan 26, 2015 at 3:42 PM, Michael Kerrisk (man-pages)
<mtk.manpages@gmail.com> wrote:
> 2. Is the API to be invoked directly by applications or is intended to
>    be used only behind specific libraries? You seem to be saying that
>    the latter is the case (here, I'm referring to your comment above
>    about sd-bus). However, when I asked David Herrmann a similar
>    question I got this responser:
>
>       "kdbus is in no way bound to systemd. There are ongoing efforts
>        to port glib and qt to kdbus natively. The API is pretty simple
>        and I don't see how a libkdbus would simplify things. In fact,
>        even our tests only have slim wrappers around the ioctls to
>        simplify error-handling in test-scenarios."
>
>    To me, that implies that users will employ the raw kernel API.

The way I read this is that there will (probably) be a handful of
users, namely the existing dbus libraries: libdus, sd-bus, glib, Qt,
ell, and maybe a few others. However, third-party developers will not
know/care about the details of kdbus, they'll just be coding against
the dbus libraries as before (might be minor changes, but they
certainly won't need to know anything about the kernel API). Similarly
to how userspace developers now code against their libc of choice,
rather than use kernel syscalls directly.

HTH,

Tom