[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    DBUS (Was: Malaga Discussions I)
From:       Waldo Bastian <bastian () kde ! org>
Date:       2005-09-02 11:04:30
Message-ID: 200509021304.33524.bastian () kde ! org
[Download RAW message or body]


On Tuesday 30 August 2005 12:39, Boudewijn Rempt wrote:
> I'm not knowledgeable like Maksim, so I'm not really entitled to an
> opinion, but if we were to break stuff, it would be good to have something
> that made writing scripts using rpc really easy. Like making the interface
> of the exposed classes completely discoverable in a way that allow authors
> of rpc client language blndings to recreate the original interface
> essentially on the fly.
>
> It's not that I'm all that happy with dcop -- especially dcop ref as a
> generic, opaque reference stub that doesn't expose the interface of the
> object it refs for is unpleasant. But I don't know whether dbus actually is
> better in that area.

If you can formulate what exactly you don't like about dcop, there is a 
possibility to fix it in dbus. At the moment dbus doesn't have anything like 
a dcopref. Not sure if I understand your concerns, but by feeding the dcopref 
in the dcop command line tool you get the interface back. It should be 
possible to do the same with dbus although dbus has a bit cleaner separation 
of the different interfaces supported by a single object.

Cheers,
Waldo



[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]