W3C home > Mailing lists > Public > public-webrtc@w3.org > July 2012

Re: checking SDP errors in SessionDescription

From: ᛏᚮᛘᛘᚤ <tommyw@google.com>
Date: Tue, 31 Jul 2012 17:20:49 +0200
Message-ID: <CALLKCfNfRGNRNCF5=Ov0TWP-Qg3RfLgfDu7zfya-M_uLKM3i4g@mail.gmail.com>
To: Li Li <Li.NJ.Li@huawei.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
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

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:28 UTC