[Remote suggestions] Interface for additional triggers for the scheduler

components/ntp_snippets/remote/remote_suggestions_scheduler.h

Index: components/ntp_snippets/remote/remote_suggestions_scheduler.h
diff --git a/components/ntp_snippets/remote/remote_suggestions_scheduler.h b/components/ntp_snippets/remote/remote_suggestions_scheduler.h
index be4c215e89b4445cd52b60b76283f7b4ed6137c4..4f61ea65c46f0cd5ea850da9a535e311ea3ae831 100644
--- a/components/ntp_snippets/remote/remote_suggestions_scheduler.h
+++ b/components/ntp_snippets/remote/remote_suggestions_scheduler.h
@@ -12,6 +12,11 @@ namespace ntp_snippets {
 // Interface for informing the scheduler.
 class RemoteSuggestionsScheduler {
  public:
+  // External triggers to consider fetching content suggestions. Returns whether
+  // a fetch will actually be triggered.
+  virtual bool OnBrowserStartup() = 0;

[tschumann, 2016/12/21 14:27:37]

is the return value actually of interest?
the caller just provides the signal, why would it care about the action the
scheduler chose?

[jkrcal, 2016/12/21 14:35:21]

Ah, you are right. I wanted to implement some histogram on the outside based on
the return value but it is actually better to do it inside the scheduler.

+  virtual bool OnNTPOpened() = 0;
+
   // Fetch content suggestions.
   virtual void OnPersistentSchedulerWakeUp() = 0;