Bug 28733 - Make sure it's easy to figure out the state of the channel (especially why it's in a certain state)
Summary: Make sure it's easy to figure out the state of the channel (especially why it...
Status: RESOLVED WONTFIX
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-24 06:01 UTC by Sjoerd Simons
Modified: 2010-10-13 03:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Sjoerd Simons 2010-06-24 06:01:59 UTC 
> * Invent a channelstate for the health of the channel
> 
> To make it easier the understand the overall state of the channel we should
> have ChannelState property with an actor. So you only have to look at this
> property to decide for example that the call ended because the other side
> rejected it, without needing to dig in the CallState property
Comment 1 Jonny Lamb 2010-10-05 06:19:05 UTC 
I don't understand this.

In your example, the call ended because the other side rejected it, so:

    CallState=Ended
    CallStateReason.Reason=User_Requested

and perhaps on top of that:

    CallStateReason.DBus_Error=ofdT.Error.NoAnswer (or similar)

and if you're paranoid then you can confirm that it was the remote user who did this with:

    CallStateReason.Actor=<the contact who rejected>

Is that right?

There's a lot to check, but that's Telepathy, and it's not so complicated. Exactly what are you suggesting?
Comment 2 Jonny Lamb 2010-10-13 03:39:30 UTC 
Sjoerd and I just decided this is pointless for now. It could come back with DRAFT3 though. We will see.

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.