On sexta-feira, 1 de novembro de 2013 09:53:45, Schaufler, Casey wrote: > > 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. > > That sounds likely to eliminate any of the performance gain kdbus provides.
Correct. The performance gains are not for non-ported applications. They are only valid for applications using D-Bus bindings that get ported. Porting the main bindings is the first step. Note that there are a number of applications -- especially system daemons -- that are not using a binding but instead are using libdbus-1 directly. Those need to be individually ported. As the QtDBus upstream maintainer, I can tell you it's not a task we were looking forward to. It's not going to be easy for us, especially considering the only person who does any work on that module is me. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
