add a couple of notes about libdbus vs. bindings

This commit is contained in:
Havoc Pennington 2004-08-10 02:18:37 +00:00
parent 7cb72cf53d
commit 138e17cce0
2 changed files with 11 additions and 1 deletions

8
README
View file

@ -5,6 +5,14 @@ See also the file HACKING for notes of interest to developers working on D-BUS.
See http://www.freedesktop.org/software/dbus/ for lots of documentation,
mailing lists, etc.
Note
===
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
===

View file

@ -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.
</para>
</listitem>
</itemizedlist>