dbus or no dbus?

Nikos Mavrogiannopoulos n.mavrogiannopoulos at gmail.com
Wed Apr 9 04:47:46 EDT 2014


Hello,
 Currently for the communication between occtl and ocserv d-bus is
being used. The seemed like a good idea initially (when I've only
heard of d-bus and kdbus), but after working a bit with it I no longer
think so. I'm considering to replace that using something simpler such
as plain unix sockets, but I'd appreciate any comments on that.

The advantages I had seen on dbus were:
1. It is available almost on every desktop and even smaller systems
(no longer think so about the latter as openwrt has its own ubus, that
is API incompatibly with dbus).
2. It would allow writing occtl in a scripting language such as python
(it didn't happen as occtl was written in C).
3. It would allow other than occtl clients to control ocserv (I had in
mind a web interface that would use d-bus to get information, but I
don't know whether that's feasible)
4. It would allow more fancy features of d-bus such as signals etc.

The disadvantages:
1. Too much code needed, and too much background things happening that
I'm not sure I can fully control its operation under ocserv.
2. It makes using occtl impossible in small systems like openwrt,
unless you can spare several megabytes to just install dbus server and
friends.

Now using something else like u-bus instead is a no-no as this thing
is only available on openwrt and nowhere else.

regards,
Nikos



More information about the openconnect-devel mailing list