[Telepathy] [Bug 19958] New: nat-traversal should be a property of stream, not channel

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=19958

           Summary: nat-traversal should be a property of stream, not
                    channel
           Product: Telepathy
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: medium
         Component: telepathy-spec
        AssignedTo: telepathy at lists.freedesktop.org
        ReportedBy: senko at senko.net


When multiple nat traversal mechanisms are supported, the choice which
one is used is not made when the channel is created, but when the
new streams are (created for incoming streams, requested for outgoing
streams).

Currently nat-traversal is property of Channel, and it is assumed that
it's known at channel creation time (e.g. for gabble it used to be
only gtalk-p2p). One workaround is to change the property when the
real data is known.

If changed mid-flight when really selected mechanism
is known, the clients might or might not pick up the change in time
(assumed they're listening to property change signals) before they
start initiating media stuff for stream that needs to have this
information (e.g. creating a farsight stream as a response to
StreamAdded), so this is very fragile.

The other reason is that on some protocols (e.g. xmpp/jingle) it is
possible (however unlikely) to have two different transport
mechanisms for two different streams in a single channel. This cannot
work at all with the current API.


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