[Bug 24906] GSM-compatible conference calls
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Mar 11 14:29:33 CET 2010
http://bugs.freedesktop.org/show_bug.cgi?id=24906
--- Comment #23 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-03-11 05:29:32 PST ---
(In reply to comment #21)
> The interface seems to be missing the mapping from channel-specific handles[*]
> to member channel object paths.
A fair point, we should think about adding that.
> Also, for client authors not wanting to deal
> with the Group interface, it might be useful to provide the change reason and
> the actor in ChannelRemoved as well.
I can only see two possibilities: the channel closed (=> more details available
from the channel's invalidation reason), and the channel was split away.
Perhaps we should define that if the channel was removed because it terminated,
then the channel must signal that it closed (and hopefully why) before
ChannelRemoved is signalled?
I don't think "client authors not wanting to deal with the Group interface" are
necessarily something we want to support. Every Conference is also a Group, and
duplicating information sems counter-productive. Is there a specific bit of
information that's too hard in the Group interface, and can we fix it in Group
instead? (Note that telepathy-qt4 and telepathy-glib both provide some
convenience API for Groups.)
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the telepathy-bugs
mailing list