+1 to Roman's comment below. No matter what additional API is produced, as long as the offer/answer state machine is there and there is SDP going between the browsers the JavaScript is either A) not actually in control of what's happening or B) manipulating a bunch of SDP and running the other side of that state machine so as to achieve that control. There's another way, we wrote it down and published it almost a year ago, and I still believe that starting with that would get us to a full spec sooner than the current path... even more so, now that the last 9 months has achieved approximately nothing. Matthew Kaufman From: Roman Shpount [mailto:roman@telurix.com] You cannot be more wrong. Each application deals with predictable set of scenarios (ones it produces) and interfaces with predictable set of non webrtc devices. These external devices are under control of the application developer. Application developer is responsible for interop with these devices. What is needed is predictable media and signaling generated by webrtc devices running the same application. With negotiation and SDP backed into the webrtc device it is very hard to achieve. So, for me as webrtc developer let me develop a negotiation scheme that works for me and make sure it stay working regardless of the browser type or version. Right now controlling webrtc application feels like driving the boat down the river by tickling the captain. _____________ Roman Shpount
Received on Friday, 19 July 2013 18:29:28 UTC