[Telepathy-commits] [telepathy-spec/master] Possible D-Bus types for the Parameters property
Alban Crequy
alban.crequy at collabora.co.uk
Wed Nov 19 06:15:04 PST 2008
20080815111806-a41c0-86b1e7e52a2f9eaeacbb99f141fe7b5609a2dab7.gz
---
spec/Channel_Interface_Tube.xml | 5 +++--
1 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/spec/Channel_Interface_Tube.xml b/spec/Channel_Interface_Tube.xml
index 7b260b6..a81e40d 100644
--- a/spec/Channel_Interface_Tube.xml
+++ b/spec/Channel_Interface_Tube.xml
@@ -48,8 +48,9 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.
<p>Each tube has a dictionary of arbitrary parameters. Parameters are
commonly used for bootstrap information. The allowable keys,
types and values are defined by the service. Connection managers
- must support the value being any primitive (non-container)
- D-Bus type, or a byte array 'ay'.</p>
+ must support the value being a string (D-Bus type 's'), array of bytes
+ (D-Bus type 'ay'), unsigned integer (D-Bus type 'u'), integer (D-Bus
+ type 'i') and boolean (D-Bus type 'b').</p>
<p>When requesting a channel with
<tp:dbus-ref namespace="org.freedesktop.Telepathy">Connection.Interface.Requests.DRAFT.CreateChannel</tp:dbus-ref>,
this property MAY be included in the request. If it is not included in
--
1.5.6.5
More information about the Telepathy-commits
mailing list