[Portland] Reminder: DAPI D-Bus API discussion on IRC

[Kevin Krammer]

Short summary:

only few people showed up, so there wasn't any extraordinary move forward.

However, an idea that seems to get positive feedback is to have the main DAPI 
service object act like a broker for the actual interfaces, i.e. instead of 
asking for Capabilities once can ask which interfaces have implementations 
and then request an implemenation for such an interface.

Additionally such an implementation can be on a different D-Bus connection, 
e.g. in a different application, in order to allow a desktop environment to 
implement some of the DAPI interfaces in their own service structure, e.g. 
implement the DAPI screensaver interface in the same process that will also 
handle the desktop's screensaver interface.

I am just not sure yet, if it is necessary to support more than one 
implementor of an interface, or if this should always be just one.

Basically the main interface could look like this:

<interface name="org.freedesktop.dapi.Broker">
    <method name="ListInterfaces">
        <arg name="interfaces" type="as" direction="out" />
    </method>
    <method name="GetInterfaceProvider">
        <arg name="interface" type="s" direction="in" />
        <arg name="connection" type="s" direction="out" />
        <arg name="path" type="o" direction="out" />
    </method>
</interface>

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freedesktop.org/archives/portland/attachments/20070215/8d8c99c5/attachment.pgp