Hi Dan, > > > One general comment before I go through it in more detail. The methods > > > dealing with Properties are redundant, since there's a standard D-Bus > > > interface specification for object properties. Check out: > > > > > > http://dbus.freedesktop.org/doc/dbus-specification.html > > > > the reason why I am for example not using the property standard in BlueZ > > is because dbus-glib is the most braindead implementation of it all. > > So what does dbus-glib have to do with it? Nothing. Whatever code > implements this will do so in the manner it likes, using dbus-glib, > libgdbus, eggdbus, or one of the other zillion libdbus rewrites out > there. Doesn't matter. > > It's simply pointless to use something else. Don't do it. It's a PITA. > Use the standardized interfaces. yeah, but I think a little bit about the languages and the bindings that are actually using these interfaces. The goal is to make their life more simple than complicated. The simpler the usage of these interfaces is for the actual client application, the better. Regards Marcel
