- From: Iñaki Baz Castillo <ibc@aliax.net>
- Date: Fri, 5 Jul 2013 11:52:20 +0200
- To: Tim Panton new <thp@westhawk.co.uk>
- Cc: Philipp Hancke <fippo@goodadvice.pages.de>, "public-webrtc_w3.org" <public-webrtc@w3.org>
2013/7/5 Tim Panton new <thp@westhawk.co.uk>: > To see what that parsing looks like - see > https://github.com/phono/PhonoSDK/blob/master/modules/phono-js/src/main/js/phono.sdp.js > > and > https://github.com/phono/PhonoSDK/blob/master/modules/phono-js/src/main/js/phono.jsep-audio.js > > Ugly, but not impossible. > > You'll notice that in phono, we parse the SDP into an object model, do whatever > we need to with it, then re-emmit the relevant output, either as XML for signalling, or as SDP for > setLocal() and friends. This is clumsy and brittle but it works ok for now. Thanks Tim. Ok, so after lot of pain you have got your scenario to work. Now some questions: - Do you desire the same level of pain for any future WebRTC application/developer? - Do you consider that the current "SDP API" is what WebRTC 1.0 deserves? - Now let's suppose that WebRTC 1.0 is out with current "SDP API" model. Do you expect that there will be a real chance for WebRTC 2.0 to drop out "SDP O/A" (once there are working deployments based on 1.0 *standard*)? Thanks. -- Iñaki Baz Castillo <ibc@aliax.net>
Received on Friday, 5 July 2013 09:53:07 UTC