Revert 39996 - Refine IPv6 probe to require that the client has an IPv6 addre...

Revert 39996 - Refine IPv6 probe to require that the client has an IPv6 address on an interface

This currently only works on Posix, not windows.

Network changes are monitored, and the test is repeated each time interfaces
change (which is a subset of any IP addresses changing).

The test performed is still relatively low latency, and we *may* need
to eventually move to an high latency test, such as a DNS resolution,
or an actual test connection.  If we move in that direction, then we'll
need to post a task to perform the work, rather than immediately returning.

BUG=25680
BUG=12754
r=wtc,eroman
Review URL: http://codereview.chromium.org/652072

TBR=jar@chromium.org

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=39998

[eroman, 2010-02-25 09:49:55]

why the revert?

[jar (doing other things), 2010-02-25 14:41:48]

There was a regression in startup perf on Mac and Linux.  It was conceivable
that the call to enumerate the interfaces was slow, and was actually causing
the problem, so I reverted.  I'll probably try to land again to verify that
this CL was the issue, and if so, look at an async way to do the probe.
 More complex probes (such as ones that waited on a resolution or a
connection) would certainly need to be run on a less critical thread, so
this structure may have to be written into place anyway.

Jim

On Thu, Feb 25, 2010 at 1:49 AM, <eroman@chromium.org> wrote:

> why the revert?
>
>
> http://codereview.chromium.org/660073
>

[wtc, 2010-02-25 21:41:10]

http://codereview.chromium.org/660073/diff/1/6
File chrome/browser/io_thread.cc (right):

http://codereview.chromium.org/660073/diff/1/6#newcode48
chrome/browser/io_thread.cc:48: if ((!net::IPv6Supported() && use_ipv6_probe) ||
Perhaps we should wait until the first hostname resolution
to call net::IPv6Supported()?