Bug 28692 - Make it clear to the streaming implementation when codecs are expected
Summary: Make it clear to the streaming implementation when codecs are expected
Status: RESOLVED FIXED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: tp-spec (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard: Call
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-23 06:23 UTC by Sjoerd Simons
Modified: 2010-10-18 08:58 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Sjoerd Simons 2010-06-23 06:23:03 UTC 
From #24936

> Re org.freedesktop.Telepathy.Call.Content.Interface.Media, comment "FIXME: How
> should the streaming implementation know when it is its turn to set the
> codecs": there should be a boolean property similar to the current
> StreamHandler.CreatedLocally, that will tell the streaming engine to defer
> setting local codecs until a remote codec offer is received.

> This could be used to avoid unnecessary codec enumeration for a received call,
> and issues with remapping payload types.
> I don't think the Creator property on Content is good for this, as it would
> force the streaming implementation to be aware of handles and the channel
> object.

The Creator property doesn't work very well it seems (especially in Muji there isn't really a creator in the first place). I'll probably remove that one. CreatedLocally is possible but again in the Muji case it's a bit more complex.
Comment 1 Jonny Lamb 2010-10-18 08:58:37 UTC 
Fixed in git.

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.