[Bug 31276] Call: Contacts are present in various places and its confusing

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Mar 15 22:03:12 CET 2011


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

David Laban <david.laban at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david.laban at collabora.co.uk
         Depends on|                            |29597

--- Comment #3 from David Laban <david.laban at collabora.co.uk> 2011-03-15 14:03:12 PDT ---
(In reply to comment #2)
> I currently think that should be only a single handle per Stream. The reason to
> have multiple handles per stream is the following use case: you have a peer
> that aggregates (but without mixing or transcoding) data from different peers.
> I don't know of any protocol that works that way. It may be better to have
> either a separate "connection" for each peer and use plain TURN instead of
> inventing something theoretical that does not exist.

As discussed on IRC, the use case for this is that if you have a server in the
sky that can multi-unicast your video without mixing then you've won because
you can avoid sending the same data 6 times over your bandwidth-limited
upstream link. Doing this over one udp socket lets you avoid all sorts of NAT
issues. This requires the ability to have multiple MediaDescriptions per
stream, and incoming data to be demuxed by SSRC.
> 
> If there is a single handle per stream, then ContactCodecMap could be split up
> and just put the RemoteCodec on each stream. They have to be matched up on both
> sides anyway. And then we can also put the CodecOffer on the Streams too (since
> it already relates on only one handle)..
> 
Veto'd. We need multiple MediaDescriptions per stream.

Please review
http://git.collabora.co.uk/?p=user/alsuren/telepathy-spec.git;a=shortlog;h=refs/heads/call-contacts
which should clarify how to deal with Contacts.

There is also a brief yak-shave to clarify LocalSendingState. Sorry about that.

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



More information about the telepathy-bugs mailing list