Bug 31136

Summary:	Add some explanation for the separation of Call.Content.I.Media
Product:	Telepathy	Reporter:	Jonathon Jongsma <jonathon>
Component:	tp-spec	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	Keywords:	patch
Version:	unspecified
Hardware:	Other
OS:	All
URL:	http://git.collabora.co.uk/?p=user/jonny/telepathy-spec.git;a=shortlog;h=refs/heads/content-interface-media
Whiteboard:	Call
i915 platform:		i915 features:

Description Jonathon Jongsma 2010-10-26 09:48:51 UTC

It's not immediately obvious why the Media interface needs to be separate from the Call.Content object itself.  It would be nice if this was justified and explained a little bit better in the documentation.

Comment 1 Jonny Lamb 2010-10-26 10:45:33 UTC

16:46 < jonner> jonnylamb, btw, do you know the reason for separating the
                Media interface from the Content?
16:47 < sjoerd> because sometimes the software isn't what controls the media
16:47 < jonner> because new-call-demo seems to have a hard assumption that
                all Content objects implement the Media interface
16:47 < jonner> oh, like dsp stuff you mean?
16:48 < sjoerd> no, like gsm phones
16:48 < sjoerd> where you just tell it to dial a number and it does that
16:48 < sjoerd> and does the audio routing in some device specific hardware way
16:48 < jonner> hm
16:48 < sjoerd> iotw tp-ring

Comment 2 Jonny Lamb 2010-10-27 02:06:08 UTC

Check out my branch.

Comment 3 Jonathon Jongsma 2010-10-27 08:11:46 UTC

Works for me.  thanks!

Comment 4 Jonny Lamb 2010-10-27 08:30:31 UTC

Thanks.

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.