Beta release of the Java implementation of dbus

Matthew Johnson dbus at matthew.ath.cx
Mon Jan 1 17:58:28 PST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

So, a bunch of work over Christmas later and I have most of a functional
D-Bus implementation in (almost) pure Java. This will form the
libjava-dbus 2.0 release and features:

    * Directly talks the wire protocol, no libdbus-1 dependency
    * No native code for TCP (and hence should just work on windows)
    * Peer-to-peer connections
    * A low-level interface
    * single-precision float type (with an environment variable set)
    * multi-threaded DBusDaemon replacement

Code is now in the dbus-java git repository on git.freedesktop.org or
can be downloaded from
http://dbus.freedesktop.org/releases/dbus-java/libdbus-java-2.0-beta.tar.gz

In implementing this I have come up against a couple of problems:

  - libdbus-1 seems to insist that the first message it gets after
    sending the Hello message is the method_return for that message. If
    you send the NameAcquired signal first (this is how my daemon is
    implemented) then it disconnects. Is this intentional? It will make
    my life somewhat harder, and I don't particularly see a reason.

  - How should I support auto-creation of busses?

  - Is there a method for detecting protocol extensions? Like alp I have
    implemented support for a single-precision float type, but it's
    unclear how to detect what the protocol in use is (particularly in a
    peer-to-peer case where there is no Hello message first which won't
    use extensions)

Matt

- -- 
Matthew Johnson
http://www.matthew.ath.cx/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFFmbxLpldmHVvob7kRAo5FAKDZZL78dzl43SIDqsF0TeWhZrRQRQCg41bX
2FO9dlwMSCZ8XtgZDALHeSs=
=7qo7
-----END PGP SIGNATURE-----



More information about the dbus mailing list