diff options
Diffstat (limited to 'spec/Connection_Interface_Anonymity.xml')
| -rw-r--r-- | spec/Connection_Interface_Anonymity.xml | 49 |
1 files changed, 33 insertions, 16 deletions
diff --git a/spec/Connection_Interface_Anonymity.xml b/spec/Connection_Interface_Anonymity.xml index 5426b5d50..4d7391891 100644 --- a/spec/Connection_Interface_Anonymity.xml +++ b/spec/Connection_Interface_Anonymity.xml @@ -21,9 +21,8 @@ 02110-1301, USA.</p> </tp:license> - <interface name="org.freedesktop.Telepathy.Connection.Interface.Anonymity.DRAFT" - tp:causes-havoc="experimental"> - <tp:added version="0.19.6">(draft version, not API-stable)</tp:added> + <interface name="org.freedesktop.Telepathy.Connection.Interface.Anonymity"> + <tp:added version="0.19.7">(as stable API)</tp:added> <tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>An interface to support anonymity settings on a per-connection basis. @@ -57,7 +56,7 @@ service level would choose both (anonymity services are opaque to clients of this interface).</p> - <p>Clients SHOULD NOT set both Client_Info and ShowClient_Info modes. + <p>Clients SHOULD NOT set both Client_Info and Show_Client_Info modes. If they are set, the CM MUST respect Client_Info and ignore Show_Client_Info.</p> </tp:docstring> @@ -68,14 +67,15 @@ <p>Explicitly request showing of client information. In connection context, this can be used to override service default. In channel context, this overrides connection anonymity modes.</p> + <tp:rationale> - In GSM, it's possible to have CLIR enabled by default, and - explicitly suppress CLIR for a single phone call. + <p>In GSM, it's possible to have CLIR enabled by default, and + explicitly suppress CLIR for a single phone call.</p> </tp:rationale> <p>Clients SHOULD NOT set both Client_Info and Show_Client_Info modes. If they are set, the CM MUST respect Client_Info and ignore - ShowClientInfo. The CM MAY set both Client_Info and Show_Client_Info + Show_Client_Info. The CM MAY set both Client_Info and Show_Client_Info in <tp:member-ref>SupportedAnonymityModes</tp:member-ref> to indicate its support for explicitly hiding and publicising client information. </p> @@ -110,21 +110,30 @@ </tp:docstring> </property> - <property name="Mandatory" type="b" access="readwrite" - tp:name-for-bindings="Mandatory"> + <property name="AnonymityMandatory" type="b" access="readwrite" + tp:name-for-bindings="Anonymity_Mandatory"> <tp:docstring> <p>This specifies whether or not the anonymity settings MUST be respected by the CM and any intermediaries between the local and remote contacts. If this is set to true but anonymity settings cannot be followed, then the session MUST be denied with a - <code>org.freedesktop.Telepathy.Errors.NotAvailable</code> error. + <code>org.freedesktop.Telepathy.Errors.WouldBreakAnonymity</code> + error. Any client that sets <tp:member-ref>AnonymityModes</tp:member-ref> SHOULD also set this property first (rather than accepting the CM's default value).</p> - <p>This property can also be set using a connection parameter in <tp:dbus-ref + <p>This property SHOULD also be made available as a parameter to + <tp:dbus-ref namespace="org.freedesktop.Telepathy.ConnectionManager">RequestConnection</tp:dbus-ref>, - see <tp:type>Conn_Mgr_Param_Flags</tp:type> for more information.</p> + with the DBus_Property flag in its + <tp:type>Conn_Mgr_Param_Flags</tp:type>. For connections managed + by the <tp:dbus-ref + namespace="org.freedesktop.Telepathy">AccountManager</tp:dbus-ref>, + clients (other than the account manager itself) SHOULD set this + property via the Account's <tp:dbus-ref + namespace="org.freedesktop.Telepathy.Account">UpdateParameters</tp:dbus-ref> + method.</p> </tp:docstring> </property> @@ -134,12 +143,20 @@ <p>The currently enabled anonymity modes for the connection. Setting has the effect of requesting new modes for the connection, and may raise an error if the unsupported modes are set. Successfully changing - the modes will result in emmision of + the modes will result in emission of <tp:member-ref>AnonymityModesChanged</tp:member-ref> signal.</p> - <p>This property can also be set using a connection parameter in <tp:dbus-ref - namespace="org.freedesktop.Telepathy.ConnectionManager">RequestConnection</tp:dbus-ref>, - see <tp:type>Conn_Mgr_Param_Flags</tp:type> for more information.</p> + <p>This property SHOULD also be made available as a parameter to + <tp:dbus-ref + namespace="org.freedesktop.Telepathy.ConnectionManager">RequestConnection</tp:dbus-ref>, + with the DBus_Property flag in its + <tp:type>Conn_Mgr_Param_Flags</tp:type>. For connections managed + by the <tp:dbus-ref + namespace="org.freedesktop.Telepathy">AccountManager</tp:dbus-ref>, + clients (other than the account manager itself) SHOULD set this + property via the Account's <tp:dbus-ref + namespace="org.freedesktop.Telepathy.Account">UpdateParameters</tp:dbus-ref> + method.</p> </tp:docstring> <tp:possible-errors> <tp:error name="org.freedesktop.Telepathy.Error.InvalidArgument"> |