stale-while-revalidate experimental implementation.

net/base/net_log_event_type_list.h

Index: net/base/net_log_event_type_list.h
diff --git a/net/base/net_log_event_type_list.h b/net/base/net_log_event_type_list.h
index 0626683a59147d0924ab7a268b0dac9a9be2332e..eb16ec701dc56b269804f6f71623b17891373567 100644
--- a/net/base/net_log_event_type_list.h
+++ b/net/base/net_log_event_type_list.h
@@ -835,6 +835,28 @@ EVENT_TYPE(HTTP_CACHE_WRITE_INFO)
 EVENT_TYPE(HTTP_CACHE_READ_DATA)
 EVENT_TYPE(HTTP_CACHE_WRITE_DATA)
 
+// Identifies the NetLog::Source() for the asynchronous HttpCache::Transaction
+// that will revalidate this entry.
+// The event parameters are:
+//   {
+//      "source_dependency": <Source identifier for the async Transaction>
+//   }
+EVENT_TYPE(HTTP_CACHE_VALIDATE_RESOURCE_ASYNC)
+
+// The stand/end of performing an async revalidation.

[yhirano, 2014/08/26 07:52:01]

start?

[Adam Rice, 2014/08/26 13:38:41]

Done.

+// For the BEGIN phase, the event parameters are:
+//   {
+//      "source_dependency": <Source identifier for the Request>
+//      "url": <String of URL being loaded>,
+//   }
+//
+// For the END phase, if there was an error, the following parameters are
+// attached:

[yhirano, 2014/08/26 07:52:01]

Seems the result is always attached.

[Adam Rice, 2014/08/26 13:38:41]

BoundNetLog::EndEventWithNetErrorCode() has a special case for OK where it just
behaves like EndEvent().

+//   {
+//      "net_error": <Net error code of the failure>,
+//   }
+EVENT_TYPE(ASYNC_REVALIDATION)
+
 // ------------------------------------------------------------------------
 // Disk Cache / Memory Cache
 // ------------------------------------------------------------------------