[Bug 28378] Channel handover

[bugzilla-daemon at freedesktop.org]

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

--- Comment #3 from Mikhail Zabaluev <mikhail.zabaluev at nokia.com> 2010-09-10 07:13:15 PDT ---
A correction to the original case: we cannot tell what channel do we hand over,
and we don't need it. It's supposed to be _the_ active channel on its protocol.

Also, the connection of the original channel is forcibly disconnected before
the handover can proceed. So the CM of the original channel needs to be
internally aware of the handover taking place, in order to not close the
channel with an error like it normally would.

Given the above, it makes sense to have handover signalling on the first
channel too. The client semantics of matching the original channel with its
successor need to allow vagueness like, "wait for the next new channel of
protocol X with Handover.TakesOverProtocol property bearing the protocol name
of the original channel".

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