KDE4's IPC

[Aaron J. Seigo]

On Friday 23 December 2005 10:53, Kevin Ottens wrote:
> Le Vendredi 23 Décembre 2005 17:38, Thiago Macieira a écrit :
> > We already do.
>
> Yes, the current situation is basically:
> session<->system : DBUS
> session<->session : DCOP
>
> I guess that this situation is not ideal, but the protocols being used for
> different purposes that's not a big issue.

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.

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".

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- 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/51e63711/attachment.sig>