Commit a8fa5571 authored by Simon McVittie's avatar Simon McVittie

Do not list Requests in the Interfaces property

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=50093Reviewed-by: Guillaume Desmottes's avatarGuillaume Desmottes <guillaume.desmottes@collabora.co.uk>
parent ab62d3c6
......@@ -67,6 +67,17 @@ USA.</p>
to have evaluated the server's functionality and enabled any extra
interfaces for the remainder of the Connection's lifetime.</p>
</tp:rationale>
<p>As a special case, the mandatory <tp:dbus-ref
namespace="imt1.Connection.Interface">Requests</tp:dbus-ref>
interface SHOULD NOT be listed in this property.</p>
<tp:rationale>
<p>It has been mandatory since Telepathy 0.18 in 2009,
and contains essential functionality for this interface,
so there seems no point in wasting bytes on capability discovery
for it.</p>
</tp:rationale>
</tp:docstring>
<tp:added version="0.19.2"/>
</property>
......
......@@ -26,10 +26,18 @@
<tp:added version="0.17.11">(as stable API)</tp:added>
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>An enhanced version of the Telepathy connection interface, which can
represent bundles of channels that should be dispatched together, and
does not assume any particular properties by which channels are
uniquely identifiable.</p>
<p>An interface for channel requests and channel lists. Under
normal circumstances, applications should deal with this
interface via the <tp:dbus-ref
namespace="imt1">ChannelDispatcher</tp:dbus-ref>,
but lower-level Telepathy applications (such as the
ChannelDispatcher itself) might need to use this interface
directly.</p>
<p>This interface is conceptually part of the core Connection
interface, but is kept separate so that its properties will
normally only need to be retrieved by the ChannelDispatcher,
and its signals will normally only wake up the ChannelDispatcher.</p>
</tp:docstring>
<tp:struct name="Channel_Details" array-name="Channel_Details_List">
......
......@@ -53,7 +53,7 @@ Interfaces=
[Protocol example]
Interfaces=
ConnectionInterfaces=im.telepathy.v1.Connection.Interface.Requests;
ConnectionInterfaces=im.telepathy.v1.Connection.Interface.Aliasing;
param-account=s required
param-password=s required secret
RequestableChannelClasses=text;
......@@ -137,6 +137,10 @@ allowed=im.telepathy.v1.Channel.TargetHandle;im.telepathy.v1.Channel.TargetID;
<code>.manager</code> file, using the key
<code>ConnectionInterfaces</code>. The corresponding value
is a list of D-Bus interface names, each followed by a semicolon.</p>
<p>As a special case, the mandatory <tp:dbus-ref
namespace="imt1.Connection.Interface">Requests</tp:dbus-ref>
interface SHOULD NOT be listed in this property.</p>
</tp:docstring>
</property>
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment