Commit 138e17cc authored by Havoc Pennington's avatar Havoc Pennington
Browse files

add a couple of notes about libdbus vs. bindings

parent 7cb72cf5
......@@ -5,6 +5,14 @@ See also the file HACKING for notes of interest to developers working on D-BUS.
See for lots of documentation,
mailing lists, etc.
A core concept of the D-BUS implementation is that "libdbus" is
intended to be a low-level API, similar to Xlib. Most programmers are
intended to use the bindings to GLib, Qt, Python, Mono, Java, or
whatever. These bindings have varying levels of completeness.
Configuration flags
......@@ -50,7 +50,9 @@
application frameworks. For example, libdbus-glib and
libdbus-qt. There are also bindings to languages such as
Python. These wrapper libraries are the API most people should use,
as they simplify the details of D-BUS programming.
as they simplify the details of D-BUS programming. libdbus is
intended to be a low-level backend for the higher level bindings.
Much of the libdbus API is only useful for binding implementation.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment