[Bug 31214] New: Call should allow multiple selected candidates and tell CM about local one

[bugzilla-daemon at freedesktop.org]

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

           Summary: Call should allow multiple selected candidates and
                    tell CM about local one
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: louis-francis.ratte-boulianne at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org


There are currently three flaws with current Call spec:

 - There is no way for the CM to know which local candidates are selected.
 - There is no way for the CM to tell which local candidates the remote
end-point chose to use (Equivalent of current SetActiveCandidatePair).
 - Only one candidate can be set as selected, even though there are usually two
(one candidate per component).

Also, I'm not really sure about how it works in conference calls. Do all
end-points use the same local candidate ? I doubt it; so we probably have to
let know the CM which end-point the local candidate was selected for as well.

One possible API could be:

Call.Stream ->
 - NewSelectedCandidate(Endpoint, Candidate) method
 - CandidateSelected(Endpoint, Candidate) signal
 - LocalSelectedCandidates({Endpoint:[Candidates]}) property

Call.Stream.Endpoint ->
 - NewSelectedCandidate(Candidate) method
 - CandidateSelected(Endpoint, Candidate) signal
 - RemoteSelectedCandidates([Candidates]) property

-- 
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.