I also think D-Bus does not seem to be appropriate for small systems. It is overkill. Also, having a library implementing all functionality and then a daemon using that library would be the best way. As Brennan mentions, in many use cases (such as mine) I would only have a single bluetooth application.
On Mon, Aug 24, 2020, at 18:41, Brennan Ashton wrote: > You are going to hate dbus :) > Honestly it is designed to be a system wide message bus for > desktop/server software and defines even a wire message format that > supports things like introspection. I think that is wrong for a > small embedded system. That leaves the question of what should be > used for IPC for the GATT server daemon. I suspect we could get far > using event file descriptors, but also just having a library where a > single application owns the GATT server is probably fine. The dbus > service is nice because I can write a standalone application that > provides the BAT service for showing battery life, and then have > another application that broadcasts RPMs from a cadence sensor. > > --Brennan >
