From kde-core-devel  Sat Oct 02 23:14:10 2004
From: Havoc Pennington <hp () redhat ! com>
Date: Sat, 02 Oct 2004 23:14:10 +0000
To: kde-core-devel
Subject: Re: RFC: DBUS & KDE 4
Message-Id: <1096758850.4452.366.camel () localhost ! localdomain>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=109675879304488

Hi,

I'm reading the thread in order so hopefully won't repeat things already
said, but here goes.

Some discussion about the dbus type system and encoding:
http://freedesktop.org/pipermail/dbus/2004-June/001169.html

See also doc/TODO as always,
http://freedesktop.org/Software/dbus/doc/TODO

Havoc

On Wed, 2004-09-29 at 18:08 +0200, Harri Porten wrote:
> On Wed, 29 Sep 2004, Lubos Lunak wrote:
> 
> >  DBUS seems to have a CUSTOM data type. Wouldn't it be sufficient to dump the
> > QDataStream-created data used by DCOP as one binary object into the custom
> > data type, or read it back using QDataStream? The apps shouldn't see any
> > difference.
> 
> Yes. But I think this should only be used for compatibility in a
> transition period. In the long run one should agree on well defined
> complex types with other projects for interoperability (via
> freedesktop.org). Example for this reasoning: a tool from the X camp might
> want to tell kdesktop to have a green background color. Speaking
> proprietary binary protocols doesn't help with integration.
> 
> Harri.