[Bug 44303] New: Call: No way to control the direction of a new Content

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Dec 30 07:09:05 CET 2011


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

             Bug #: 44303
           Summary: Call: No way to control the direction of a new Content
    Classification: Unclassified
           Product: Telepathy
           Version: git master
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: tp-spec
        AssignedTo: telepathy-bugs at lists.freedesktop.org
        ReportedBy: olivier.crete at ocrete.ca
         QAContact: telepathy-bugs at lists.freedesktop.org


There are 4 different ways a content can be added (at the start of the call or
later and by the local side or by the remote side). The spec as currently
written doesn't allow to control the initial direction in any of these cases. 
suggest the following:

1. Allow calling of SetSending()/RequestReceiving() on initial streams before
the Accept() call to set the direction in the initial offer and answer.

2. On streams added after the call is started, set the "LocalSendingState" to
PENING_SEND if the other side creates a stream asking us to send.

3. For Contents created with AddContent(), it's a bit touchy.. ie I have no
idea how to do it with the current API short of adding another argument to
AddContent() or adding a Accept() to the Content itself, all of which is a bit
nasty. This is problematic as it could be a privacy leak too... I think we
could want to create a stream to just ask the other side to send.

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