stale-while-revalidate experimental implementation.

chrome/common/chrome_switches.h

Index: chrome/common/chrome_switches.h
diff --git a/chrome/common/chrome_switches.h b/chrome/common/chrome_switches.h
index e216f6b86e7e846f67284558c89956b8aea320e9..5a0a1103eed893ac152c0ca033a848c691b9b313 100644
--- a/chrome/common/chrome_switches.h
+++ b/chrome/common/chrome_switches.h
@@ -103,6 +103,7 @@ extern const char kDisableSavePasswordBubble[];
 extern const char kDisableSearchButtonInOmnibox[];
 extern const char kDisableSessionCrashedBubble[];
 extern const char kDisableSpdy31[];
+extern const char kDisableStaleWhileRevalidate[];
 extern const char kDisableSuggestionsService[];
 extern const char kDisableSync[];
 extern const char kDisableSyncSyncedNotifications[];
@@ -173,6 +174,7 @@ extern const char kEnableSpdy4[];
 extern const char kEnableSpellingAutoCorrect[];
 extern const char kEnableSpellingFeedbackFieldTrial[];
 extern const char kEnableSSLConnectJobWaiting[];
+extern const char kEnableStaleWhileRevalidate[];

[rvargas (doing something else), 2014/09/11 02:33:06]

why 2 arguments?

[Adam Rice, 2014/09/12 01:46:48]

I don't know. Some things have Enable/Disable pairs and some don't.

I don't know what criteria to use to make a decision.

[rvargas (doing something else), 2014/09/12 18:33:12]

We should not have two arguments with opposite meaning. I suspect sometimes we
end up with two because we start with a disable-by-default logic and later move
to enable-by-default without cleaning the code.

 extern const char kEnableStreamlinedHostedApps[];
 extern const char kEnableSuggestionsService[];
 extern const char kEnableSyncArticles[];