Commit 0f705e0f authored by Simon McVittie's avatar Simon McVittie

Import ChannelDispatcher.I.Messages from Mission Control master

My main concern about this interface was whether implementing it
caused MC to be unmaintainable, but it isn't too bad in practice,
just unfinished.

The one edit here, relative to Mission Control, is making the
filename end with "1.xml" instead of "_DRAFT.xml", so that
subsequent diffs on the contents aren't lost in the rename noise.

Bug: https://bugs.freedesktop.org/show_bug.cgi?id=37380Reviewed-by: Guillaume Desmottes's avatarGuillaume Desmottes <guillaume.desmottes@collabora.co.uk>
parent f4b552a8
<?xml version="1.0" ?>
<node name="/Channel_Dispatcher_Interface_Messages_Draft"
xmlns:tp="http://telepathy.freedesktop.org/wiki/DbusSpec#extensions-v0">
<tp:copyright>Copyright (C) 2011 Collabora Ltd.</tp:copyright>
<tp:copyright>Copyright (C) 2011 Nokia Corporation</tp:copyright>
<tp:license xmlns="http://www.w3.org/1999/xhtml">
<p>This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2.1 of the License, or (at your option) any later version.</p>
<p>This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.</p>
<p>You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
USA.</p>
</tp:license>
<interface
name="org.freedesktop.Telepathy.ChannelDispatcher.Interface.Messages.DRAFT"
tp:causes-havoc="not yet final">
<tp:requires interface="org.freedesktop.Telepathy.ChannelDispatcher"/>
<tp:docstring xmlns="http://www.w3.org/1999/xhtml">
<p>
This interface allows DBus clients to use the ChannelDispatcher to
send one-off text messages to a contact, identified by account and
target ID, without requiring the caller to handle channels or be
the primary message UI.
</p>
<tp:rationale>
<p>
This enables entities other than the main UI to send messages
to contacts.
</p>
</tp:rationale>
</tp:docstring>
<method name="SendMessage" tp:name-for-bindings="Send_Message">
<arg direction="in" name="Account" type="o"/>
<arg direction="in" name="TargetID" type="s"/>
<arg direction="in" name="Message" type="aa{sv}"
tp:type="Message_Part[]"/>
<arg direction="in" name="Flags" type="u"/>
<arg direction="out" name="Token" type="s"/>
</method>
</interface>
</node>
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