Massively simplify the NetworkChangeNotifier infrastructure:

  * Use a process-wide object (singleton pattern)
  * Create/destroy this object on the main thread, make it outlive all consumers
  * Make observer-related functions threadsafe

As a result, the notifier can now be used by any thread (eliminating things like NetworkChangeObserverProxy and NetworkChangeNotifierProxy, and expanding its usefulness); its creation and inner workings are much simplified (eliminating implementation-specific classes); and it is simpler to access (eliminating things like NetworkChangeNotifierThread and a LOT of passing pointers around).

BUG=none
TEST=Unittests; network changes still trigger notifications
Review URL: http://codereview.chromium.org/2802015

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@50895 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 2 deletions

diff --git a/chrome/browser/io_thread.h b/chrome/browser/io_thread.h
index 9708509..60e3a40 100644
--- a/chrome/browser/io_thread.h
+++ b/chrome/browser/io_thread.h
@@ -26,7 +26,6 @@ class Predictor;
 
 namespace net {
 class HttpAuthHandlerFactory;
-class NetworkChangeNotifier;
 class URLSecurityManager;
 }  // namespace net
 
@@ -34,7 +33,6 @@ class IOThread : public BrowserProcessSubThread {
  public:
   struct Globals {
     scoped_ptr<ChromeNetLog> net_log;
-    scoped_ptr<net::NetworkChangeNotifier> network_change_notifier;
     // TODO(willchan): Stop reference counting HostResolver.  It's owned by
     // IOThread now.
     scoped_refptr<net::HostResolver> host_resolver;