checking SDP errors in SessionDescription

When constructing a SessionDescription from a SDP string received from a peer, the SDP string may contain syntactic errors (according to RFC4566) as it may have been manipulated by the remote application.

I think the browser should catch these errors during the construction of SessionDescription object, through  error callback or exception. By detecting an invalid SDP early, the application can be more robust and efficient.

The current API can catch these errors in setRemoteDescrition() through its error callback. However, this requires a PeerConnection object.


Received on Tuesday, 31 July 2012 15:07:02 UTC