KDE4's IPC

[Kevin Ottens]

Le Vendredi 23 Décembre 2005 21:29, Aaron J. Seigo a écrit :
> there is the cost involved in having a multiplicity of APIs, which is why i
> suppose you are getting with "not ideal". having one API for
> session<->session IPC and one for session<->system means people have to
> master more API, which raises the bar further.

Yes, that's exactly "not ideal". Who said euphemism? ;-)

Currently, it seems that the burden is only on people working on kdelibs since 
that's where most session<->system communication happen for us. But I'm 
pretty sure it'll change...

> and as more DBUS services appear, it'll just get to be a more and more
> confusing mish-mash of "dcop here, dbus there, dcop under there".

And in particular when services inside the session will be available... it'll 
be a real mess from here.

Regards.
-- 
Kévin 'ervin' Ottens, http://ervin.ipsquad.net
"Ni le maître sans disciple, Ni le disciple sans maître,
Ne font reculer l'ignorance."
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051223/f061b7f1/attachment.sig>