diff options
| author | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2013-11-11 18:48:46 +0000 |
|---|---|---|
| committer | Simon McVittie <simon.mcvittie@collabora.co.uk> | 2013-11-11 18:48:52 +0000 |
| commit | 98f46d75ff6d8db8c6b2f5d7472f6ddbcb6c9a36 (patch) | |
| tree | 3112cab0ff4e47f5b71ca46ec70f5a6769b6e2d0 /spec/Channel_Type_Server_TLS_Connection1.xml | |
| parent | 7e3ae0c0d58ad6c163b3ba83c15cedf430228a1c (diff) | |
Update spec to 0.99.5
Preliminary version of this patch reviewed by Xavier Claessens.
Bug: https://bugs.freedesktop.org/show_bug.cgi?id=71262
Signed-off-by: Simon McVittie <simon.mcvittie@collabora.co.uk>
Diffstat (limited to 'spec/Channel_Type_Server_TLS_Connection1.xml')
| -rw-r--r-- | spec/Channel_Type_Server_TLS_Connection1.xml | 18 |
1 files changed, 9 insertions, 9 deletions
diff --git a/spec/Channel_Type_Server_TLS_Connection1.xml b/spec/Channel_Type_Server_TLS_Connection1.xml index 89fe43c65..a0a5b412e 100644 --- a/spec/Channel_Type_Server_TLS_Connection1.xml +++ b/spec/Channel_Type_Server_TLS_Connection1.xml @@ -18,26 +18,26 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. </tp:license> - <interface name="im.telepathy1.Channel.Type.ServerTLSConnection1"> + <interface name="im.telepathy.v1.Channel.Type.ServerTLSConnection1"> <tp:added version="0.19.13">(as stable API)</tp:added> - <tp:requires interface="im.telepathy1.Channel"/> + <tp:requires interface="im.telepathy.v1.Channel"/> <tp:docstring xmlns="http://www.w3.org/1999/xhtml"> <p>A channel type that carries a TLS certificate between a server and a client connecting to it.</p> <p>Channels of this kind always have <tp:dbus-ref - namespace="im.telepathy1.Channel">Requested</tp:dbus-ref> = False, - <tp:dbus-ref namespace="im.telepathy1.Channel">TargetHandleType</tp:dbus-ref> - = None and <tp:dbus-ref namespace="im.telepathy1.Channel">TargetHandle</tp:dbus-ref> + namespace="im.telepathy.v1.Channel">Requested</tp:dbus-ref> = False, + <tp:dbus-ref namespace="im.telepathy.v1.Channel">TargetHandleType</tp:dbus-ref> + = None and <tp:dbus-ref namespace="im.telepathy.v1.Channel">TargetHandle</tp:dbus-ref> = 0, and cannot be requested with methods such as <tp:dbus-ref - namespace="im.telepathy1.Connection.Interface.Requests">CreateChannel</tp:dbus-ref>. + namespace="im.telepathy.v1.Connection.Interface.Requests">CreateChannel</tp:dbus-ref>. Also, they SHOULD be dispatched while the - <tp:dbus-ref namespace="im.telepathy1">Connection</tp:dbus-ref> + <tp:dbus-ref namespace="im.telepathy.v1">Connection</tp:dbus-ref> owning them is in the CONNECTING state.</p> <p>In this case, handlers SHOULD accept or reject the certificate, using the relevant methods on the provided object, or MAY just <tp:dbus-ref - namespace="im.telepathy1.Channel">Close</tp:dbus-ref> the channel before doing so, to fall + namespace="im.telepathy.v1.Channel">Close</tp:dbus-ref> the channel before doing so, to fall back to a non-interactive verification process done inside the CM.</p> <p>For example, channels of this kind can pop up while a client is connecting to an XMPP server.</p> @@ -48,7 +48,7 @@ tp:immutable='yeah'> <tp:docstring> <p>A <tp:dbus-ref - namespace="im.telepathy1.Authentication">TLSCertificate</tp:dbus-ref> + namespace="im.telepathy.v1.Authentication">TLSCertificate</tp:dbus-ref> containing the certificate chain as sent by the server, and other relevant information.</p> </tp:docstring> |