[OfflinePages] Restarts immediate processing if stopped due to no net

components/offline_pages/background/connection_notifier.h

+// Copyright 2016 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef COMPONENTS_OFFLINE_PAGES_BACKGROUND_CONNECTION_NOTIFIER_H_

[Pete Williamson, 2016/12/01 01:34:08]

I think I recall you saying something about NQE also having a notifier.  If I
remember correctly, why chose this one over that one?  (Either is fine, I just
want to make sure we thought about it.)

[dougarnett, 2016/12/01 19:25:22]

I think there is no difference for what this class does currently - callback 
on next connection type seen. I did not see any difference yet in chattiness
between disconnecting and reconnecting (which was what I was wondering about).
The NQE can generate more events when you are connected and the connection
quality is determined to have changed. If/when we want to differentiate between
poor and non-poor connections, then we will want to use NQE here.

+#define COMPONENTS_OFFLINE_PAGES_BACKGROUND_CONNECTION_NOTIFIER_H_
+
+#include "base/callback.h"
+#include "net/base/network_change_notifier.h"
+
+namespace offline_pages {
+
+class ConnectionNotifier
+    : public net::NetworkChangeNotifier::ConnectionTypeObserver {
+ public:
+  // Callback to call when we become connected.
+  typedef base::Callback<void()> ConnectedCallback;
+
+  ConnectionNotifier(const ConnectionNotifier::ConnectedCallback& callback);
+  ~ConnectionNotifier() override;
+
+ private:
+  // net::NetworkChangeNotifier::ConnectionTypeObserver implementation.
+  void OnConnectionTypeChanged(
+      net::NetworkChangeNotifier::ConnectionType type) override;
+
+  base::Callback<void()> callback_;
+
+  DISALLOW_COPY_AND_ASSIGN(ConnectionNotifier);
+};
+
+}  // namespace offline_pages
+
+#endif  // COMPONENTS_OFFLINE_PAGES_BACKGROUND_CONNECTION_NOTIFIER_H_