DBUS message formats
John (J5) Palmieri
johnp at redhat.com
Mon Dec 12 05:44:12 PST 2005
The only thing that uses XML is the introspection format. The message
format is binary and being that we are almost ready to ship 1.0 unless
there is a really good reason to switch, we won't. Many smart people
have worked on D-Bus and given their input. We value yours but it is
kind of late to the game. We feel our approach is the right one and if
it is not then let it be bested by real world alternatives rather than
BTW OO programming is a way of thinking not a language. D-Bus's API is
very much centered around objects.
On Mon, 2005-12-12 at 13:50 +0100, Gerrit van der Bij wrote:
> Hi there,
> I've read the documentation that accompanies the debian package of
> dbus-1, in particular the message formats.
> I agree with XML having far too much overhead. Binary protocols are
> better suited for the purpose of IPC.
> I have been experimenting with writing my own SNMP-engines in JAVA, and
> at the heart of SNMP lies the ASN.1 BER specification. (ASN.1 Binary
> Encoding Rules)
> This is a binary specification which is (nearly) as lightweigth as the
> message protocol used by DBUS.
> So I wondered: Wouldn't it be more practical to adopt the ASN.1 BER
> specification for your messages ?
> That way, you can write the specification of the message format in the
> ASN.1 language, which is a standard for these kind of things.
> (In the long term, the DBUS messages could be sent via SNMP to other
> machines, and vice versa)
> I'd offer my coding skills but I've just migrated from C to object
> oriented programming and I am blissfully unaware of how to code anything
> else than a single executable..
> Gerrit van der Bij
> dbus mailing list
> dbus at lists.freedesktop.org
John (J5) Palmieri <johnp at redhat.com>
More information about the dbus