Patrick Ohly wrote:
Hello!
Here's a more formal description of the D-Bus server<->clients (plural!)
interface for user dialogs or other information provisioning by clients.
I have pushed the description to the dbus-api branch. If this is okay,
then I'll also add stubs to the server's source code.
I know that the "'source name' backend" string will be difficult to
localize. Feel free to ignore this, almost none of the backends
currently need it. Only very advanced usages like accessing Exchange via
EDS currently do.
Looks good to me...
<signal name="InfoRequest">
<doc:doc>
<doc:description>
<doc:para>
Emitted whenever the server needs information that only a
client can provide. Because the server does not know whether
clients are monitoring it (attaching to the server is
optional) and/or which of the attached clients are able to
handle the request, it broadcasts the request.
</doc:para>
<doc:para>
Clients respond by calling InfoRequest. The flow is this:
should be "Clients respond by calling InfoResponse".
- Jussi