Bug 20156 - MediaSignalling: interactive transport negotiation
Summary: MediaSignalling: interactive transport negotiation
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard: Call
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-17 03:44 UTC by Simon McVittie
Modified: 2011-02-11 06:50 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Simon McVittie 2009-02-17 03:44:37 UTC 
From my streamedmedia branch:

"""
There is currently no way for clients to influence the choice of transport: in general, a client making a call can't know the capabilities of the streaming implementation, or even which streaming implementation will be used (channels will often be requested by an address book or similar application that will not handle the channel itself).

If a mechanism for transport negotiation is added, it should be something that happens after the request, but before calling Media.SessionHandler.Ready, so that it is the streaming implementation that chooses the transport, rather than the requesting client.
"""
Comment 1 Simon McVittie 2010-11-10 06:45:56 UTC 
I think this is fixed in Call (in which case we can close this bug as WONTFIX) but I'm not completely sure.
Comment 2 Olivier Crête 2010-11-10 07:17:05 UTC 
Can't the CM know what's available from the Tp Capabilities ? What's the goal exactly ?
Comment 3 Olivier Crête 2011-02-11 06:50:57 UTC 
There is InitialTransport in the Call Channel

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.