Remove the HostResolver::Shutdown() method....

Remove the HostResolver::Shutdown() method.
While this doesn't entirely remove the hack, it limits the scope of it to HostResolverImpl.
Hopefully in the future HostResolver will not be refcounted so this can go away altogether.

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

[eroman, 2010-02-04 01:54:40]

Minor cleanup...

[willchan no longer on Chromium, 2010-02-04 21:42:04]

lgtm, i just have some commenting nits

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

http://codereview.chromium.org/569035/diff/1/7#newcode132
chrome/browser/io_thread.cc:132: // TODO(eroman): hack http://crbug.com/18373
Why'd you change the bug id here?  18373 doesn't seem to provide useful info in
the bug description.  I note that in host_resolver_impl.h your TODO references
bug id 15513.  It seems like you should be consistent in your bug reference,
whichever you choose.

[eroman, 2010-02-05 05:07:12]

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

http://codereview.chromium.org/569035/diff/1/7#newcode132
chrome/browser/io_thread.cc:132: // TODO(eroman): hack http://crbug.com/18373
On 2010/02/04 21:42:04, willchan wrote:
> Why'd you change the bug id here?  18373 doesn't seem to provide useful info
in
> the bug description.  I note that in host_resolver_impl.h your TODO references
> bug id 15513.  It seems like you should be consistent in your bug reference,
> whichever you choose.

Done. (reverted to old bug number).

I will do a post-cleanup and make these consistent -- basically I don't want
this to point at a closed bug, so would rather link to the "remove hack" bug,
and have that bug describe what the original problem was.

[willchan no longer on Chromium, 2010-02-05 18:41:08]

in case you were waiting for my comment, it still lgtm