one of the primary advantages of using the dbus type system in dconf is the theoretical posibility of using it from any language by way of the dbus bindings already in that language.

currently you can only perform writes via dbus (using the dbus-writer) and even then you have to have some knowledge of the topology of the dconf database (ie: you need to know that writes to "/user/" have to go to "ca.desrt.dconf.writer.user", and so on).  reads would require using libdconf to read the database file directly.

dconf should have a dconf service that can be used by anyone who wants to access it via dbus.  this interface should do everything that libdconf normally does for applications that use it.