Status of dbus-python

[David Sommerseth]

On 28/03/18 23:00, Lawrence D'Oliveiro wrote:
>>> Do you know if libdbus (and on top of that your bindings) can use
>>> kdbus as the underlying server/daemon?
>>>
>>     (am trying to guess the correct terminology here. By server/daemon
>>     I mean the underlying mechanism that actually conveys the
>> dbus-messages. kdbus is the faster, kernel based, mechanism as
>> opposed the previously used userspace daemon [didn't get the name of
>> that one])
>
> As Simon said, kdbus was proposed as a kernel patch and rejected. I
> gather the developers are working on a new thing called BUS-1 ...

Just echoing this.  Things are happening here, but not too openly.  I spoke
with one of the developers involved with kdbus/bus1 a while ago, and he said
things where progressing - but they wanted to ensure they had all bases
covered first before sending anything more to the kernel list.  And then
Varlink appeared earlier this year too.

I do know there was some talk about providing a D-Bus compliant daemon with
bus1, which mostly would be a broker between D-Bus applications and the kernel
bus1 interface.

Some references:

Bus1: a new Linux IPC proposal
<https://lwn.net/Articles/697191/>

Bus1 Kernel Message Bus
<https://lwn.net/Articles/704731/>

Varlink: a protocol for IPC
<https://lwn.net/Articles/742675/>

I would generally consider kdbus a dead end now.  To me it seems most
developers tries to figure out something more acceptable for the kernel
community.  Until that happens, I'd sit still on the fence and wait.


-- 
kind regards,

David Sommerseth