- From: Emil Ivov <emcho@jitsi.org>
- Date: Wed, 29 Jan 2014 08:51:58 +0100
- To: Justin Uberti <juberti@google.com>
- Cc: Roman Shpount <rshpount@turbobridge.com>, Peter Thatcher <pthatcher@google.com>, "public-orca@w3.org" <public-orca@w3.org>
Hey all, On Wed, Jan 29, 2014 at 2:53 AM, Justin Uberti <juberti@google.com> wrote: > Emil, does Peter's suggestion work for you? Yes, it does, thanks! On Wed, Jan 29, 2014 at 1:56 AM, Peter Thatcher <pthatcher@google.com> wrote: > Also, is it enough to require JS to poll? Why not have an event for > when the values change? +1. While polling is obviously much better than nothing at all, having a change event would be quite convenient. > Since we only care about the latest values, can't we just throttle how > often the event is fired? Say, every 200ms? When you say "we", do you mean the application or the browser? If the application has control over the throttling then that's OK. With regard to energy levels, there are two main use cases: * acting on changes of the current speaker (e.g. in order to upscale their corresponding video and thumbnail everyone else) * showing energy levels for all participants For both of them, I'd expect granularity preferences to vary from one application to the next. Emil -- https://jitsi.org
Received on Wednesday, 29 January 2014 07:52:46 UTC