>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.
I'm not sure if I understand your answer correctly. If not, please let me know. We have ported the kdbus transport layer which is implemented by Samsung at the libdbus. It's not needed to port individually when a application is using libdbus directly. Best Regards, Hyungjun. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
