> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Thiago Macieira > Sent: Saturday, November 02, 2013 2:16 PM > To: [email protected] > Subject: Re: [Dev] [RFC] kdbus transport for DBus > > On sábado, 2 de novembro de 2013 12:15:33, Schaufler, Casey wrote: > > Why do I feel like I'm missing something? > > > > We want kdbus to improve performance. > > Yes. > > > Many/most/some dbus applications will require porting. > > Yes. > > > That is too much work, so we need a compatibility daemon that is going > > to suck away any performance gain, and in fact probably make > > performance worse. > > Quite possibly. > > > We're counting on the widespread adoption of kdbus in the future, > > which will get the performance back as everyone ports everything from > dbus to kdbus. > > Yes. > > > I can see kdbus as a long term plan. > > > > 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. > > > 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.
Then why are we discussing how to implement it for Tizen 3? I know it's not ready, you know it's not ready, but there's a whole bunch of discussion about how to work around the fact that it's not ready. That sounds like "we're going ahead anyway". > -- > Thiago Macieira - thiago.macieira (AT) intel.com > Software Architect - Intel Open Source Technology Center _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
