[Bug 26807] Mute interface for Channel.Type.Call

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=26807

--- Comment #17 from Senko Rasic <senko at senko.net> 2010-05-06 01:21:50 PDT ---
(In reply to comment #15)
> (In reply to comment #14)
> > Another possibility is to just not implement Mute in XMPP at all or add a
> > property to the interface to say its only an informational message (and that it
> > does not actually Mute anything).
> 
> I think a D-Bus method called Mute() which doesn't actually mute anything would
> be surprising... ☺

Instead of (Request)Mute() that behaves erratically, or hinting mute-ing by
changing directions which CMs should then ignore (even more bizzarre :), can we
just have Muted(b:muted) method, and say:

"""
This is an informational message from the client to the cm, to inform it that
the client has muted the Call.Content. Client is responsible for (un)muting
itself (e.g. by muting the microphone or shutting off the camera). Client MUST
call this whenever it mutes or unmutes the content.

Rationale: for some protocols, the fact that the content is muted needs to be
transmitted to the peer; for others, the notification to the peer is only
informational (eg. XMPP), and some protocols may have no notion of muting at
all.
"""

(Also: in this case, do we need elaborate state changes?)

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.