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

Re: Transport change in MS Proposal

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 29 Aug 2012 14:35:32 -0700
Message-ID: <CABkgnnXnq8YiOqxh8LmEuCv2tZHmLmXnZK3D3D1GZyifk=QBUg@mail.gmail.com>
To: Li Li <Li.NJ.Li@huawei.com>
Cc: "public-webrtc@w3.org" <public-webrtc@w3.org>
On 29 August 2012 12:35, Li Li <Li.NJ.Li@huawei.com> wrote:
> Martin,
> In the MS proposal [1], a JS application has the ability to change the transport for a RealtimeMediaStream object, when detecting the transport bandwidth is too low through JS callback.
> Since JS execution cannot be interrupted by callbacks, what happens if the callback is delayed by a long running JS block?

Javascript should not block in this way.  If your javascript does not
return control to the browser at least 60 times a second, people are
going to notice some performance degradation.  Even assuming that you
are operating slower than this, I'm not sure what you imagine would be
so time-sensitive as to require this sort of reaction time.

Received on Wednesday, 29 August 2012 21:36:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:17:32 UTC