Re: Recap from WebRTC World

On Tue, Jul 23, 2013 at 10:56 PM, cowwoc <cowwoc@bbs.darktech.org> wrote:

>  On 24/07/2013 1:50 AM, Göran Eriksson AP wrote:
>
>
>    - Troubleshooting WebRTC: There is a gaping hope when it comes to
>    user-facing diagnostic tools.
>
>  Just to make sure I understand Your point- could You elaborate in what
> You mean and add some concrete proposals? Do You for instance mean the
> stats API?
>
>  Hi Göran,
>
>     Imagine you wrote a production web conferencing app and customers are
> calling tech support saying "It doesn't work" where do you begin?
>
>     A good starting point is looking at Skype. Skype provides a
> user-friendly UI that gives a quick overview of potential network,
> hardware, configuration problems and allows you to drill-down for more
> information. I am asking for:
>
>    - A user-facing UI that allows you to drill down from a high to low
>    level.
>    - Make this functionality available through an API so applications can
>    collect this information programmatically and, say, refund a user if a
>    meeting was aborted due to no fault of his own.
>
>     One problem I found very hard to diagnose (in development, not to
> mention production) is why I was getting smooth video at home but choppy
> video at a customer's location. Is the bandwidth too low? Is the latency
> too high? Is the router dropping UDP packets? Is the CPU usage too high
> (leading WebRTC to drop frames)? Etc... It goes on and on. The stats API
> dumps a lot of information (too much for me to parse quickly, obviously)
> but even with all this information it's hard to come up with a conclusive
> answer to these actions.
>
Well, I certainly agree that this function is useful, but it's the job of
the
Web application to deliver, not the browser.

-Ekr