[Bug 46386] New: document that requested stream directions can be unattainable, or make it discoverable

[bugzilla-daemon at freedesktop.org]

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

             Bug #: 46386
           Summary: document that requested stream directions can be
                    unattainable, or make it discoverable
    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: simon.mcvittie at collabora.co.uk
         QAContact: telepathy-bugs at lists.freedesktop.org
                CC: olivier.crete at ocrete.ca


In Gabble:

> + if (initial_direction == TP_MEDIA_STREAM_DIRECTION_NONE)
> + {
> + g_set_error (error, TP_ERRORS, TP_ERROR_INVALID_ARGUMENT,
> + "Jingle can not do contents with direction = NONE");
> + return NULL;
> + }

and

> f (initial_direction != TP_MEDIA_STREAM_DIRECTION_BIDIRECTIONAL)
> + {
> + g_set_error (error, TP_ERRORS, TP_ERROR_NOT_IMPLEMENTED,
> + "Adding un-directional contents is not supported"
> + " in MUC channels");
> + return NULL;
> + }

For the first case, it seems reasonable for the spec to say that CMs might not
support contents whose streams' initial direction is NONE, and that clients
SHOULD NOT ask for this (although the error should probably be NotAvailable or
something - InvalidArgument generally implies "you got it wrong, you suck"
rather than "sorry, this protocol can't do what you asked").

For the second case, I think we should have a way for UIs to discover whether
unidirectional contents will work or not, so they can avoid having UI for it in
this case.

My understanding of Call is pretty shaky, so I might be misunderstanding either
or both of those: if so, please correct me.

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