Blocking server calls

[ldo]

Blocking server calls

[ldo]

Is this another library also using libdbus?

[TheMeaningfulEngineer]

Somewhere below it is, combined with the glib's event loop.

[ldo]

So can you get back a DBusConnection pointer from it?

[TheMeaningfulEngineer]

It uses dbus.SystemBus() from dbus-python. That kind of looks like the best candidate I have atm for what you've asked. :)

https://github.com/getsenic/gatt-python/blob/master/gatt/gatt_linux.py#L33

[ldo]

DBussy is not compatible with dbus-python. As far as I know, there is no way to ask the latter for the underlying DBusConnection pointer from libdbus. Sorry.

[TheMeaningfulEngineer]

All good, thanks.

Just for me to understand, to be able to have a dbus interface registered there needs
to be an event loop running (or any kind of a dedicated d-bus application) somewhere to maintain it?

When I referred to:

dbussy to expose a D-bus connection with blocking code

I was coming with an analogy of spraying a message on a wall. Where a wall was the underlying system bus, and spraying a message was the the synchronous blocking call. So once you spray the paint it it stays on the wall regardless of the spray can. Seems like this was wrong :)

[ldo]

DBussy stores the underlying libdbus pointers as low-level ctypes.c_void_p values, so you can peek at these and take your life in your hands with it if you choose. But dbus-python hides all that within its C code, where you can’t get at it.