as you may have seen in the past from my postings to this list, I
started to work on a D-Bus language binding for ooRexx, which now is
more or less concluded and enters a testing phase of a few months before
announcing and making it available to the public (a student will stress
test and experiment with it).
If there are Linux users here, who are interested in experimenting with
this D-Bus language binding, for ooRexx then please drop me an e-mail
with a subject of "ooRexx DBus testing" and I will make the binding
(package has 32- and 64-bit shared libraries and an installation script
that should be able to install it correctly on various kinds of Linux
systems) and a draft of an overview article available to you. The
request would be to learn about your experiences, errors and
Ad D-Bus: D-Bus was originally created at Red Hat and got turned over to
the freedesktop.org such that it can be incorporated into all Linux
distributions for many years by now.
D-Bus is a wire protocol with a message broker allowing programs in
different processes to communicate with each other (even between
different computers if employing the tcp transport). Usually the Linux
kernel communicates events via (the "system") D-Bus signal messages and
any D-Bus signal listeners may learn about these events (e.g.
adding/removing devices etc.).
In addition for each session a "session" D-Bus daemon/broker, which
allows one to interact with Linux applications.
To put it into different words: D-Bus is for Linux, what OLE/ActiveX is
for Windows: a communication infrastructure allowing to easily interact
with applications (remote control them, learning about their
More about D-Bus, its concepts and ooRexx snippet examples in the draft
of the overview article.
So, if I was able to wet your appetite a little bit, then please drop me
P.S.: D-Bus ports are available for MacOSX and Windows as well.
Therefore (for experimental reasons) I have also created ports of the
ooRexx language bindings for these platforms. I was even able to have a
Linux, a Windows and a MacOSX computer communicate with an ooRexx D-Bus
service object via TCP/IP. The clients would run on all systems and
interact with the service object in separate tests on Linux, MacOSX and
Windows. More about this, if the initial tests for D-Bus on Linux work
out for those interested.