[Bug 34640] New: Use Protocol.IdentifyAccount to choose accounts' object paths

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed Feb 23 23:55:06 CET 2011


https://bugs.freedesktop.org/show_bug.cgi?id=34640

           Summary: Use Protocol.IdentifyAccount to choose accounts'
                    object paths
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: mission-control
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: will.thompson at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


The specification says that, when constructing a new account's object path
(which is its persistent identifier):

  The account manager SHOULD choose acct such that if an account is deleted,
  its object path will be re-used if and only if the new account is in some
  sense "the same" (incorporating the 'account' parameter in some way is
  recommended)

MC doesn't really respect this all that well: it guesses based on the 'account'
parameter, but this doesn't cut it for protocols like IRC.

Since spec version something recent, there's been a method that CMs can
implement to turn a dictionary of parameters into a unique identifier for the
account, suitable for MC to use when building the object path:
<http://telepathy.freedesktop.org/spec/Protocol.html#Method:IdentifyAccount>.
MC should use it, where possible. This also allows MC to prevent you creating
two copies of the same account.

For backwards compatibility, the object paths for existing accounts should be
preserved, but we could stash the CM's preferred identifier alongside the
account to avoid having to repeatedly retrieve it as discussed on bug 34416.

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



More information about the telepathy-bugs mailing list