How does D-Bus differ from DCOP?
Start by reading Q:9. D-Bus is intentionally pretty similar to DCOP, and can be thought of as a “DCOP the next generation” suitable for sharing between the various open source desktop projects. D-Bus is a bit more complex than DCOP, though the Qt binding for D-Bus should not be more complex for programmers. The additional complexity of D-Bus arises from its separation of object references vs. bus names vs. interfaces as distinct concepts, and its support for one-to-one connections in addition to connections over the bus. The libdbus reference implementation has a lot of API to support multiple bindings and main loops, and performs data validation and out-of-memory handling in order to support secure applications such as the systemwide bus. D-Bus is probably somewhat slower than DCOP due to data validation and more “layers” in the reference implementation. A comparison hasn’t been posted to the list though. At this time, KDE has not committed to using D-Bus, but there have been discussi
