--nextPart3415560.dzlbnlk3lE
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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=20
D-BUS applications. Let me explain:

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

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

=2D-=20
  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

--nextPart3415560.dzlbnlk3lE
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQBBWtkZM/XwBW70U1gRAuxRAKCi4gdCw4catvncm0y4x41CPvWcGwCfRR9s
i0QQjL39QVgg+QZmrQQZR68=
=pfra
-----END PGP SIGNATURE-----

--nextPart3415560.dzlbnlk3lE--