[Bug 28378] Channel handover

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Mikhail Zabaluev <mikhail.zabaluev at nokia.com> 2010-08-20 06:54:03 PDT ---
There is another, slightly different case: fallback during call initiation.

The scenario is as follows:
1. A client requests a call channel.
2. The request dispatcher requests the channel from the most suitable
connection on connection manager #1 chosen accordingly to some logic (more on
that later).
3. The CM#1 tries to establish the call, but meets a condition telling it that
the call is better made using a different connection. It signals call
disconnection with a (detailed) error indicating this condition.
4. The request dispatcher continues with the logic from step 2 and chooses
another connection on CM#2, also suitable for the call request.
5. The handler client tries to make sense of it all, getting either both or
only the second of the channels to handle as the call depending on how we
decide to represent this case.

To allow this, we may need to:
- Allow channel request semantics by which the handler will only get the
eventually successful channel. It is not yet clear at which point a channel can
be considered successful and past the possibility for failover.
- Allow the handover property for the successor channel to be requestable, so
the UIs can treat it the same way as channel handovers initiated by protocol.

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