On 11/02/2013 10:16 PM, Thiago Macieira wrote: > On sábado, 2 de novembro de 2013 12:15:33, Schaufler, Casey wrote:
>> I can see kdbus as a long term plan. >> I see lots of work and a system that does not perform as well as it does >> today with "real" dbus. >> >> Someone please tell me what I'm missing. > > You're missing that kdbus is still not ready for prime time. It's not, but the problem is that it won't be ready for long time unless somebody will start to actually use it. This is what this work is all about. Casey rightly pointed out that kdbus is long term plan, that requires quite a lot of work. This work has to start some day. >> I can't image why it makes any sense at all for Tizen3. > > Nor I. Unless there are specific gains to be had for specific > daemons that we plan on porting, I don't see the point of going > ahead of upstream. Upstream plays mostly with libsystemd-bus, which doesn't really have that many clients. Personally I do see benefit in trying to use kdbus in real system with real applications. Honestly, I don't believe that all of libdbus-1 clients will be rewritten to either linux-specific libsystemd-bus or glib. Will it always be required to carry dbus1-to-kdbus bridge for purpose of these applications? I'm not sure, but in this context libdbus-kdbus port certainly has some potential. Cheers Karol _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
