Dear Roman, Till now no one in the working group has confirmation, that in what form WebRTC1.0 will be finally shipped. So based on the difference of WebRTC1.0 and WebRTC2.0, backward compatibility should be supported. But that will be decided later. It may be maintaining of two API's, old and new, or providing some JS wrapper for the old API or some other format. This can be decided only after confirming shipped WebRTC1.0 and finalizing what to be shipped in WebRTC2.0. Thanks, Kiran. On Sun, Jul 21, 2013 at 4:55 AM, Roman Shpount <roman@telurix.com> wrote: > On Sat, Jul 20, 2013 at 6:25 PM, Peter Thatcher <pthatcher@google.com>wrote: > >> I'm curious: As a web developer, if 2.0 were a great API that allowed >> you to never touch SDP, would it matter to you if it were backward >> compatible with 1.0? How would that negatively impact you? >> >> >> > The issue here is no SDP. It is offer/answer. If I still need to go > through offer/answer state machine to control things, then it affects me > negatively. If we have two parallel APIs, one with SDP and offer/answer and > one without then I would be fine. The other issue would be the amount of > effort that maintaining 1.0 API with offer/answer would take for web > browser developers. If this will take priority over 2.0 we would all lose. > _____________ > Roman Shpount > >
Received on Sunday, 21 July 2013 04:28:01 UTC