[Bug 42932] Call: Content.Removed has not reason, but Call.ContentRemoved has one

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2011-12-15 03:10:10 PST ---
(In reply to comment #1)
> Lets just remove the duplicated signal

For the record, the reason for the duplicated signal was that if you only have
a client-side proxy object for a Content and not for its parent Channel, you
can't tell when the Content has gone away. I'd be happy for that to be resolved
by "don't do that, then", though.

If the Content is implicitly considered to have gone away when the Channel
closes (which I suspect it ought to) or when the Connection disconnects (which
it certainly should), then TpCallContent needs to get a TpCallChannel and a
TpConnection in its constructor anyway, to be able to connect to the
appropriate invalidation signals.

-- 
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.