From kde-core-devel  Fri Sep 02 10:37:31 2005
From: Waldo Bastian <bastian () kde ! org>
Date: Fri, 02 Sep 2005 10:37:31 +0000
To: kde-core-devel
Subject: DBUS (Was: Malaga Discussions I)
Message-Id: <200509021237.36213.bastian () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=112565756215792
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1241739.6PRAhNeFBx"

--nextPart1241739.6PRAhNeFBx
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Sunday 28 August 2005 19:09, Maks Orlovich wrote:
> On Sunday 28 August 2005 07:00, Stephan Kulow wrote:
> > The first one was IPC. We once again summarized the benefits of KDE
> > switching to DBUS (among the lines of 'well maintained', 'support from
> > toolkits and other desktops', 'distribution support already very high')
> > and what bothers us with it ('C API', 'unsolved performance problems',
> > 'unknown upgrade path').
>
> Here, I have to express disappointment (most of the points have to do with
> hype and not anything technical), though I am hardly surprised (see
> 'hype'). Perhaps I am mistaken, but has D-Bus reached any sort of API, AB=
I,
> and wire compatibility stability? Has the protocol been properly specifie=
d?
> (If the wire compatibility is stable, and the spec is finally reasonably
> complete, I can probably do a client implementation in a weekend).

Yes, it is stable but not yet entirely set in stone, which is great because=
 it=20
means that if you discover a problem with it it, it can still be fixed now.=
 I=20
expect D-BUS to have a API/ABI stable 1.0 release well before KDE 4.0.

Cheers,
Waldo

--nextPart1241739.6PRAhNeFBx
Content-Type: application/pgp-signature

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

iD8DBQBDGCtwN4pvrENfboIRAv5MAJ4/43cwN/D1XWfI+W/gzXHqJkS/tgCdGoPU
CfR6w9ovXT030yEryuLnJ6E=
=vWbI
-----END PGP SIGNATURE-----

--nextPart1241739.6PRAhNeFBx--