Skip to main content

Ralsina.Me — Roberto Alsina's website

D-BUS: a systemwide bus / IPC system

The link goes to a mes­sage by Hav­oc Pen­ning­ton de­scrib­ing D-BUS, a IPC tech­nol­o­gy be­ing de­vel­oped for use in Red Hat, and per­haps as a fu­ture (think 18 month­s) re­place­ment for DCOP and maybe Bonobo's IPC mech­a­nis­m.

Sounds nice, at least what I can un­der­stand of the spec­s, and adopt­ing it should­n't cause any big trau­ma on the KDE side, since our DCOP class­es are au­to­gen­er­at­ed by macros any­way. Hope­ful­ly, it may even be source com­pat­i­ble.

Lots more in­for­ma­tion, in­clud­ing the specs and an in­ter­est­ing take on KDE-G­NOME co­op­er­a­tion by Miguel de Icaza if you fol­low the links a lit­tle.

Navindra Umanee / 2006-04-03 04:24:

God does Mailman threading suck! But that was a good read... The Miguel's stuff is in the March archive for the desktop-devel-list for anyone looking for it.

Sad Eagle / 2006-04-03 04:25:

I don't we can truly switch to a different IPC format in a fully source-compatible manner since a lot of places still use QDataStream directly/manually to marshall DCOP arguments for calls (as opposed to the new nice-and-magic DCOPRef template stuff; obviously the receiving end stuff is auto-gen'ed).. However, one could probable just encapsulate DCOP over DBus by using some sort of a raw/unformatted message feature.. With that BC would probably be possible too.. But wire compat... Well, let's not talk about that :-)



Contents © 2000-2020 Roberto Alsina