[Bug 46386] 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

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2012-02-23 05:10:20 PST ---
(In reply to comment #1)
> For the MUC case it's really that I didn't take the time to understand the muji
> code in gabble enough to propagate the information correctly.

OK, great. I'll clone a bug.

> I think that once it's fully implemented, it woudl have the same protocol
> restriction that NONE isn't allowed.

Is there any valid reason why a UI might want to set a stream to be
"no-directional"?

If there is, we should have some sort of flag to say "not possible" so it can
not display that option, or something. (Or invert it, and have a flag for
protocols like SIP where it *is* possible - I think I'd prefer that, actually.)

If there isn't, we should say that CMs might not support contents whose
streams' initial direction is NONE, and that clients SHOULD NOT ask for it.

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