RFC: DBUS & KDE 4

[Thiago Macieira]

Thiago Macieira wrote:
>- write a DCOP-to-DBUS bridge (dcopserver being a D-BUS client, maybe?)
>which would relay messages from DCOP to the D-BUS environment.

Complementing myself:

KDE3 applications using native DCOP would not be able to access non-KDE4 
D-BUS applications. Let me explain:

KDE4 applications using our D-BUS implementatino would register DCOP alias 
names inside the D-BUS namespace "org.kde.dcop.appname.objname".  
Therefore, if a DCOP call is received on our KDE4 dcopserver, it can be 
routed to the KDE4 application using D-BUS.

However, those KDE3 applications using DCOP would not be able to call 
"obj.freedesktop.screensaver", since there would be no DCOP alias for them. 
I don't believe this to be a problem since KDE3 applications cannot call 
that *now*. Since their view of the world is already restricted *now*, we 
wouldn't do any harm by *not* enhancing that view.

-- 
  Thiago Macieira  -  Registered Linux user #65028
   thiago (AT) macieira (DOT) info
    ICQ UIN: 1967141   PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- 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/20040929/dec0318f/attachment.sig>