[telepathy-spec/master] fd.o #14620: declare that Connect is idempotent

Simon McVittie simon.mcvittie at collabora.co.uk
Mon Apr 13 07:37:27 PDT 2009


This matches existing practice, and the assumptions made in telepathy-glib,
libtelepathy and Mission Control.
---
 spec/Connection.xml |   17 +++++++----------
 1 files changed, 7 insertions(+), 10 deletions(-)

diff --git a/spec/Connection.xml b/spec/Connection.xml
index 39fb738..6245475 100644
--- a/spec/Connection.xml
+++ b/spec/Connection.xml
@@ -45,17 +45,14 @@ USA.</p>
     </tp:struct>
 
     <method name="Connect" tp:name-for-bindings="Connect">
-      <tp:docstring>
-        Request that the connection be established. This will be done
-        asynchronously and errors will be returned by emitting
-        <tp:member-ref>StatusChanged</tp:member-ref> signals.
-      </tp:docstring>
+      <tp:docstring xmlns="http://www.w3.org/1999/xhtml">
+        <p>Request that the connection be established. This will be done
+          asynchronously and errors will be returned by emitting
+          <tp:member-ref>StatusChanged</tp:member-ref> signals.</p>
 
-      <tp:possible-errors>
-        <tp:error name="org.freedesktop.Telepathy.Error.NotAvailable">
-          The connection is already connecting or connected
-        </tp:error>
-      </tp:possible-errors>
+        <p>Calling this method on a Connection that is already connecting
+          or connected is allowed, and has no effect.</p>
+      </tp:docstring>
     </method>
 
     <method name="Disconnect" tp:name-for-bindings="Disconnect">
-- 
1.5.6.5



More information about the telepathy-commits mailing list