stale-while-revalidate experimental implementation.

net/base/load_flags_list.h

Index: net/base/load_flags_list.h
diff --git a/net/base/load_flags_list.h b/net/base/load_flags_list.h
index 72792eb9aaba4ac351fc357d796d9ac5a7fa7d9f..f2f4f2580a97de643277afa3b5684f88b87abdcf 100644
--- a/net/base/load_flags_list.h
+++ b/net/base/load_flags_list.h
@@ -125,3 +125,8 @@ LOAD_FLAG(DO_NOT_USE_EMBEDDED_IDENTITY, 1 << 27)
 // reduction proxy.
 // TODO(rcs): Remove this flag as soon as http://crbug.com/339237 is resolved.
 LOAD_FLAG(BYPASS_DATA_REDUCTION_PROXY, 1 << 28)
+
+// Indicates the the request is an asynchronous revalidation. Currently this
+// flag just prevents re-entering the async code path, so you probably don't

[rvargas (doing something else), 2014/09/05 22:52:39]

nit: The comment risks becoming stale without noticing. When we move issuing the
request above the cache there has to be a way to tell the cache not to serve
stale content again, right?

[Adam Rice, 2014/09/09 12:36:45]

I removed the comment. I'm still concerned about creating a false expectation
that it does something exciting and wasting people's time.

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

Fair point. We could consider naming this closer to what it does as opposed to
the type of request, but I guess we can wait for a more complete implementation
before deciding the final name. (I mean, if this is a flag for the cache to do
validations in a certain way, as it seems it is, it should be next to all the
other cache-related flags)

+// want to use it.
+LOAD_FLAG(ASYNC_REVALIDATION, 1 << 29)