Enable experimental BWE by default in AppRTC about samples

[marwahvikas]

Thanks will work on it.

[marwahvikas]

Looked into it, seems like need to add constraint googImprovedWifiBwe set to true. Do we want to have this as a url param to enable/disable it as well?

[juberti]

Just set it to true universally.

On Thu, May 1, 2014 at 3:35 PM, Vikas Marwaha [email protected]:

Looked into it, seems like need to add constraint googImprovedWifiBwe set
to true. Do we want to have this as a url param to enable/disable it as
well?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-41964848
.

[marwahvikas]

sure thanks!

[cowwoc]

What is the meaning of googImprovedWifiBwe?

[juberti]

It was an experimental change to our bandwidth estimation algorithm. The
experiment was successful and it is now on by default in Chrome 36.
On May 21, 2014 5:36 PM, "cowwoc" [email protected] wrote:

What is the meaning of googImprovedWifiBwe?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-43817461
.

[cowwoc]

Is it too technical to explain how you treat Wifi and non-Wifi connections differently under this new algorithm?

[juberti]

We didn't treat wifi differently, we just improved the algorithm to deal
better with some issues that were seen in congested wifi networks.

On Wed, May 21, 2014 at 7:03 PM, cowwoc [email protected] wrote:

Is it too technical to explain how you treat Wifi and non-Wifi connections
differently under this new algorithm?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-43825585
.

[juberti]

Fixed in #24