Why this change? sdps are in a way “complicated” in plaintext but at the same time, for those who works with these monsters for a long time, they are also clear and meaningful.
wrapping them with an hand written library could lend to undesired behaviors, and it will be way more complicated to debug issues since sdps generated by the browser and these received by the agent aren’t the same.
Is there a specific reason for this introduction?
There is also a major problem with this changes that probably breaks lots of integrations and will force us to stick to the v3: interoperability.
I know that lots of people using licode in a production environment, are also using a probably hand made native app for android and ios or a open source project such as Zevarito’s excellent work .
There’s no such library that translates sdps in JSON and there’s no way (correct me if i’m wrong) we can spend such lot of time to write one.
I think this highly-customised way to send sdps is a “regression” in my point of view and there has to be a way to exchange sdps in plaintext as before.
I hope you’ll get my point.
Please share your thoughts guys