On Jan 15, 2011, at 11:05 AM, Jose Antonio Santos Cadenas wrote: > Hi, > > 2011/1/14 Daniel Wagner <wagi@xxxxxxxxx>: >> From: Daniel Wagner <daniel.wagner@xxxxxxxxxxxx> >> >> Hi Johan, >> >> During some connman debug session I found some small hickups in the >> introspection code in gdbus. Marcel ask me to check with you first. >> > > I've been thinking about the way that dbus is used in BlueZ and I am > concerned about why we don't use glib-dbus instead of dbus directly. > This way the dbus specific code will be maintained by glib-dbus. > > I've thought it several times and I've never said anything because is > a big change and as everything was working I preferred not to make > noise with this. But now that some bugs appeared we can probably think > on this changing the BlueZ DBus code and all the plugins interfaces. > The only problem I see is that this will probably require a version > change because the way plugins expose their interface will change. One (big) thing that makes me not to like glib-dbus is having to cope with GObject. ALso, it makes certain things more complicated and convoluted than they are in low-level API (e.g passing an array), it is poorly documented, and, incredibly enough, lacks things like the uint16 type. My feeling goes the other way round: I wish we had the gdbus API *outside* BlueZ, as a library, so any C application could enjoy it.-- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
