FYI, here is a perfect example of how SDP is being abused:
1. I ask for the ability to constrain the minimum/maximum bandwidth
used by WebRTC:
https://code.google.com/p/webrtc/issues/detail?id=1327
<https://code.google.com/p/webrtc/issues/detail?id=1327&can=4&colspec=ID%20Pri%20Mstone%20ReleaseBlock%20Area%20Status%20Owner%20Summary>
2. This issue is "blocked by":
https://code.google.com/p/webrtc/issues/detail?id=1349
3. https://code.google.com/p/webrtc/issues/detail?id=1349 is closed
with the following comments
1. "These are not actually exposed through PeerConnection, only
through the C++ API, right? Maybe we should adjust the title of
the bug."
2. "Those are exposed to JS through SDP already."
Someone needs to communicate to the Chrome committers that exposing
functionality to JS "through SDP" is not acceptable. Meaning,
https://code.google.com/p/webrtc/issues/detail?id=1349 should be reopened.
Gili
Received on Wednesday, 3 July 2013 17:23:58 UTC