OCT
13
2000

DCOP bindings for Java

Matthias Hoelzer-Kluepfel recently announced Java bindings for DCOP. In other words, Java can now communicate with and control KDE2 applications. A welcome addition to the existing C bindings for DCOP, originally used by the long gone kmapnotify. Then, of course, there's kxmlrpc which provides a bridge to DCOP for anything that can speak HTTP and XML (eg, control DCOP-speaking apps from a shell script or python). And as if all that wasn't enough, there's the command-line or point-n-shoot DCOP browser/executor that just goes to show how far, flexible and mature DCOP has become in a short matter of time. Simplicity pays off in the end.

Comments

This sounds really interesting (javadcop). I'll have to try it once I find the time to install this on my box. If something useful comes out of it, I'll let you know ...

cu

D

"Real programmers don't comment their code.
It was hard to write, it should be hard to understand."


By Dominik Niedermeier at Fri, 2000/10/13 - 5:00am

Will there ever be such a thing as kSOAP?


By Antonie Fourie at Fri, 2000/10/13 - 5:00am

Yes probably. There is already kxmlrpc which supports the similar XMLRPC protocol. SOAP is somewhat more complicated, but it will probably be added when someone has time.

Rich.


By Richard Moore at Fri, 2000/10/13 - 5:00am

Absolutely! I wrote kxmlrpcd back before SOAP was announced (XMLRPC is a precursor to SOAP) and never got around to updating it. I'll be working on ksoapd (or whatever) after 2.0.


By Kurt Granroth at Sat, 2000/10/14 - 5:00am

What's the point? If I wanted to write an app with KDE support, I would write a native KDE app, in C++, etc. The whole point of Java is to write cross-platform programs, which are not tied to any particular operating system. Don't get me wrong, I like KDE, but lets not add 'non-WORA' extensions to Java.


By Slava Pestov at Sun, 2000/10/15 - 5:00am

Java is a nice language, making it work well with KDE is the Right Thing (tm) to do. This only adds to the power of Java, not removes.


By ac at Mon, 2000/10/16 - 5:00am

Because you should have the opertunity to to whatever
you'd like.
And if you think component architecture, you can be sure that you once need to communicate with
an already existing component....!


By Nils Olav Selåsdal at Fri, 2000/10/20 - 5:00am

Instead of DCOP, they should called it ROBOCOP as in Realtime OBject Oriented COP!


By ac at Tue, 2000/10/17 - 5:00am