Re: [GIT PULL] kdbus for 4.1-rc1
From: Havoc Pennington
Date: Wed Apr 15 2015 - 13:42:24 EST
On Wed, Apr 15, 2015 at 1:20 PM, Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:
> I read a bit of the documentation, but not enough. I really need to sit
> down and play with code. That's the way I learn and understand.
It might be useful for some of the current devs to post about the best
APIs to play with these days - my old libdbus is pretty painful,
compared to some of the newer stuff.
gdbus nicely shows a callback-based way to handle owning a service,
using a function like g_bus_own_name:
The callback-based approach means the library can handle
reconnection/restart on behalf of the app.
The flip side (the way you use rather than provide a service) looks similar:
Here the library can deal with complexities of a service being
restarted, the app only has to write the callbacks so they can be
called more than once (with alternating appeared/vanished handlers).
You can see in those API docs more of the ordering guarantees, in this
case on callback invocation - less for apps to screw up.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/