Re: [rtcweb] Proposal for a JS API for NoPlan (adding multiple sources without encoding them in SDP)

[Robin Raymond <[e-mail]>]

Then why not move to a lower level API and do it as a shim (i.e. reverse 
polyfill)?

If provided a lower level API that works without SDP where the 
individual network/media component wiring/attributes can be controlled, 
we could create the same WebRTC API that exists today for people who 
think "SDP out to be enough for anybody" layered on top of it; They lose 
absolutely nothing (in fact they gain a lot since now they can tweak the 
logic to be even more compatible with their networks and dynamically 
update it as needed instead of waiting for the next browser "patch" to 
be deployed everywhere on all platforms). The only different is that 
it's an JavaScript implementation rather than written in C++. They get 
what they want but we get what we need.

That's the difference, they *want* this API as it "works/good enough for 
them", whereas many of *need* a lower level API to do anything 
sophisticated at all. As it stands, it makes many use cases for us who 
whom don't want to do basic SIP/SDP signaling extremely challenging, 
complex, ugly, brittle, if not outright impossible. I've explained many 
times why using SDP with offer/answer is horribly bad idea (and I can 
re-share those links if needed).

-Robin


> Peter Thatcher <mailto:[e-mail]>
> 19 June, 2013 11:15 AM
>
>
>
> I hope so as well.  Unfortunately, Microsoft's input seems to be "our 
> way or the highway" and the input of others seems to be "SDP ought to 
> be enough for anybody".  My thinking is that we can make incremental 
> improvements toward a cleaner API without being so extreme at either 
> end.  And I hope I can find others that think similarly.
>
>