diff options
Diffstat (limited to 'spec/Connection_Interface_Requests.xml')
| -rw-r--r-- | spec/Connection_Interface_Requests.xml | 15 |
1 files changed, 1 insertions, 14 deletions
diff --git a/spec/Connection_Interface_Requests.xml b/spec/Connection_Interface_Requests.xml index 7d7ec0eb..f9c751f6 100644 --- a/spec/Connection_Interface_Requests.xml +++ b/spec/Connection_Interface_Requests.xml @@ -396,11 +396,7 @@ <arg name="Channels" type="a(oa{sv})" tp:type="Channel_Details[]"> <tp:docstring> - The channels and their details. All channels that are signalled - together like this MUST have the same - <tp:dbus-ref namespace="im.telepathy1.Channel.FUTURE">Bundle</tp:dbus-ref> - property, which may - either refer to an existing bundle, or establish a new bundle. + The channels and their details. </tp:docstring> </arg> </signal> @@ -551,15 +547,6 @@ between the properties, so we do not have separate arrays of required and optional properties.</p> </tp:rationale> - - <p>If this array contains the - <tp:dbus-ref namespace="im.telepathy1.Channel.FUTURE">Bundle</tp:dbus-ref> - property, then this class of channel can be combined with other - channels with that property in a request, or added to an existing - bundle. If not, this signifies that the connection manager is - unable to mark channels of this class as part of a bundle - this - means that to the remote contact they are likely to be - indistinguishable from channels requested separately.</p> </tp:docstring> </tp:member> </tp:struct> |