On Wed, Jun 19, 2013 at 10:45 AM, cowwoc <cowwoc@bbs.darktech.org> wrote: > > Disregarding the whole section about replacing Offer/Answer since I > believe it is out of scope for this discussion, are you asking for a > Javascript API that interacts directly with WebRTC without having to pass > through a blob/opaque-token? I agree the latter is not ideal, but at the > end of the day what's the big deal? If vendors want SDP and end-users want > a Javascript API, agreeing to a blob is a decent compromise. > > Since you are disregarding the main point of discussion, there is no point to discuss it any further. The problem is not SDP. The problem is Offer/Answer. Creating API object layers on top of SDP is a waste of time. What you are proposing does not address the underlying issue. Changing from string blob to an object does not give us anything except slightly better cosmetics. It is putting lipstick on a pig. The issue is ability to change media session settings without renegotiating all the settings in the session. You should be able to change transmit codec without going through offer/answer. You should be able to disable echo canceler and noise suppression without going through offer answer. You should be able to add video to an existing audio session without disturbing the audio and doing the offer/answer. Also, if you read the discussion carefully, you will realize that O/A with SDP will never be accepted as a browser interface. It is too complex, not easily testable, and cannot be defined in a way that allows interoperable implementations. The sooner it is going to be scrapped the sooner we will get something that can be a standard. I was quiet a few previous months waiting for this group to realize what corner that got themselves into. Now, with bundle discussions and with real life implementation experience I think the group is getting ready to move on to something productive. _____________ Roman Shpount
Received on Wednesday, 19 June 2013 15:00:26 UTC