[Dev] [RFC] kdbus transport for DBus

Thiago Macieira thiago.macieira at intel.com
Fri Nov 1 15:34:33 GMT 2013


On sexta-feira, 1 de novembro de 2013 14:25:48, Carsten Haitzler wrote:
> e_dbus and eldbus (the e one(s)) use libdbus - so if libdbus ports to
> kdbus.. efl will be fine. :)

That's not going to happen. libdbus-1 will not be ported because the codebase 
is too hard to work with. One of the major sources of performance problems in 
D-Bus is the recursive marshalling code in that library, which was written in 
2005 and was never optimised.

In order to support applications that haven't been ported, kdbus will provide 
a bus converter. That is, it will launch a separate daemon instead of dbus-
daemon that will create the expected socket addresses and will do on-the-fly 
translation from the protocol 1 messages on Unix sockets to protocol 2 
messages on kdbus.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131101/7af15b74/attachment.asc>


More information about the Dev mailing list