Bug 28723 - Need to document/design how to handle codec negotiation failures
Summary: Need to document/design how to handle codec negotiation failures
Status: RESOLVED DUPLICATE of bug 35573
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: http://git.collabora.co.uk/?p=user/al...
Whiteboard: Call
Keywords: patch
Depends on:
Blocks:
 
Reported: 2010-06-24 05:30 UTC by Sjoerd Simons
Modified: 2011-03-31 10:30 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Sjoerd Simons 2010-06-24 05:30:00 UTC 
From #24936:


> Sjoerd says we also need to think about what happens if a change to codecs via
> SetCodecs() but a remote contact doesn't like it.
Comment 1 Olivier Crête 2011-02-11 11:15:08 UTC 
Add reason to ContentRemoved signal

ContentRemove(o: Content, u: enum, s: dbus error, s: Message)
Comment 2 David Laban 2011-03-08 10:25:36 UTC 
Sketched it up in http://git.collabora.co.uk/?p=user/alsuren/telepathy-spec.git;a=shortlog;h=refs/heads/remove-reason

Can anyone think of any more reasons to put in the enum? I currently have Requested, Codec_Negotiation_Failed, Hardware_Fault, Network_Fault.
Comment 3 Olivier Crête 2011-03-22 15:44:59 UTC 
I think that Content.RemoveContent() should not have a reason (isn't it always user-requested in this case?).. And errors from the media layer are reported in the .I.Media interface.. Or did I miss some case where the UI wants to remove a Content without the user's request ?

Also, the enum is duplicated between the Call and Content interfaces.

Sorry for not seeing this bug earlier.
Comment 4 David Laban 2011-03-31 10:30:01 UTC 

*** This bug has been marked as a duplicate of bug 35573 ***

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.