[Halevt-dev] [RFC] dbus/python branch

[Raphaël]

Hi,
I just pushed a new implementation in the git repository.
(was quickly discussed before) :

- it entierly relies on dbus and dbus introspection :
A daemon (like udisks or upower) is registrered as a dbus service thus
provides Objects, Properties, Signals and Methods but also a listing of what
values it returns, what signal name we can attach to, ... that's
introspection.
(these are also documented in the XML service description file usually found
in /usr/share/dbus-1/*)

- it **may** be generic enough (it attempts to catch the current
hardware discovery workflow at the dbus specification level) but hasn't
even been tested with upower so far ...

- uses XSLT as much as possible : the configuration is written in XML, the dbus
services specifications are written in XML

- as a POF it is implemented in python but the most complex part being
the "Configuration / Object Specification" "merge", even a larger part
of this work could be implemented in XSLT to be language agnostic to use
as much simple bricks as possible.

The configuration schema probably needs to be modified (a DTD exists but
isn't really flexible enough to be heavily used at config-load time) to
support setting properties of objects from different services like, eg,
plug storage device X (udisks) while "on battery" (upower), ...
And the TODO list is probably not exhaustive.

Any thoughts, advices, criticisims, improvements, alternatives,
... welcomed

Raphaël