I am very sceptical of those, specifically for the multi stream case. So
far the plan is to go for native ORTC support.
Even if they did work as a drop-in replacement though (which I really don't
expect) there would likely still be a ton of things to address around the
frontend side. So all in all I still find "you had better implement
it rather than adding a warning screen" to be a bit of an unfair comment
On Thursday, 12 May 2016, Ingo Bauersachs <email@example.com> wrote:
> Not exactly comparable efforts. We do have ORTC on our roadmap and we
> have it scheduled for soon, but will probably be quite a while before we
> even close to a prototype.
Last I've read is that there are already adapter-libs mapping ORTC to
> So I agree with Boris.
dev mailing list
Unsubscribe instructions and other list options:
sent from my mobile