Re: checking SDP errors in SessionDescription

But what would you use a SessionDescription object for if you don't have an
PeerConnection?

/Tommy

On Tue, Jul 31, 2012 at 5:04 PM, Li Li <Li.NJ.Li@huawei.com> wrote:

>  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. ****
>
> ** **
>
> Thanks.****
>
> Li****
>
> ** **
>
> ** **
>



-- 
Tommy Widenflycht, Senior Software Engineer
Google Sweden AB, Kungsbron 2, SE-11122 Stockholm, Sweden
Org. nr. 556656-6880
And yes, I have to include the above in every outgoing email according to
EU law.

Received on Tuesday, 31 July 2012 15:21:17 UTC