From kde-core-devel  Sun Feb 12 19:52:16 2006
From: Michael Pyne <michael.pyne () kdemail ! net>
Date: Sun, 12 Feb 2006 19:52:16 +0000
To: kde-core-devel
Subject: Re: kde3support
Message-Id: <200602121501.16437.michael.pyne () kdemail ! net>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=113977393630703
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1408627.p6or8y0zrv"

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

On Sunday 12 February 2006 11:12, Thiago Macieira wrote:
> Jaroslaw Staniek wrote:
> >Why to kill compatibility (and predictability) after all these "let's
> > make DCOP a selling point for KDE" talks?

Well, KDE3 applications will still talk to other KDE3 applications as well.

One problem is that it is hard to do, since AFAIK all that dcopserver knows=
=20
about the passing data is that it is a QByteArray.  That is, the dcopserver=
=20
couldn't automatically transform a QString into the DBUS equivalent, becaus=
e=20
the dcopserver doesn't know that the destination is expecting a QString.

We could manually interpret some of the well known interfaces as Thiago=20
mentioned, but it is an impossible general-case problem.  Especially for=20
applications that never had a DCOP IDL (their DCOP interface is entirely=20
in-code).

This is true even if we're not switching to DBUS, since the on-wire interfa=
ce=20
to QByteArray of some types changed in Qt 4.  An application would have to=
=20
manually ask for the old interface to ensure compatibility.  This isn't as=
=20
difficult a problem as we could fix it by altering dcopidl for the 99% of=20
applications that use a DCOP IDL.  But I'd hate to be the one trying to tes=
t=20
that setup. :-/

Regards,
 - Michael Pyne

--nextPart1408627.p6or8y0zrv
Content-Type: application/pgp-signature

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

iD8DBQBD75QMqjQYp5Omm0oRAocnAJsEbIAcZw26DLeHy7y7i1198EBOXwCfbX4j
enLPBtJWKH/kYsVKimwOQi8=
=P4L2
-----END PGP SIGNATURE-----

--nextPart1408627.p6or8y0zrv--