[Telepathy] [Bug 14620] New: Decide whether Connection.Connect() should be idempotent

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=14620

           Summary: Decide whether Connection.Connect() should be idempotent
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: ASSIGNED
          Severity: minor
          Priority: medium
         Component: telepathy-spec
        AssignedTo: telepathy at lists.freedesktop.org
        ReportedBy: simon.mcvittie at collabora.co.uk


libtelepathy and telepathy-glib assume that it's OK to call Connect() when the
Connection is in the CONNECTING state.

telepathy-glib's tp_connection_run_until_ready() goes further, assuming that if
the library user requested that Connect() be called if necessary, then it's OK
to call it even before we know what the status is (i.e. before the first
GetStatus() has returned).

In practice, I believe all Connect() implementations are idempotent, and
silently return success at all times (unless the object has been destroyed as a
result of a failed attempt to connect).

However, the spec says:

<tp:error name="org.freedesktop.Telepathy.Error.NotAvailable">
          The connection is already connecting or connected

(the markup is wrong though, so it doesn't show up in the HTML).

I'm inclined to say that Connect() should indeed be idempotent, and we should
remove this possible error.

(When we've decided which it should be, please tell mardy - MC makes a similar
assumption.)


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.