On Fri, 01 Nov 2013 08:34:33 -0700 Thiago Macieira <[email protected]> said:
> 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. aaah ok - so things will work - we'll have a bridge, but it won't be optimal. to be optimal we need to port to kdbus directly. grrrr. at least that gives us time to do it - doesn't become a major show-stopper priority. -- Carsten Haitzler (The Rasterman) <[email protected]> _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
