Prepare to add more initiator info to CachedResource(Request)

Source/core/loader/cache/CachedResource.h

Index: Source/core/loader/cache/CachedResource.h
diff --git a/Source/core/loader/cache/CachedResource.h b/Source/core/loader/cache/CachedResource.h
index 6473ec448426e3201e2e01f19983775cec636cda..90741d9e4e088be235938372233195cf857adbfe 100644
--- a/Source/core/loader/cache/CachedResource.h
+++ b/Source/core/loader/cache/CachedResource.h
@@ -27,6 +27,7 @@
 #include "core/loader/FrameLoaderTypes.h"
 #include "core/loader/ResourceLoaderOptions.h"
 #include "core/loader/cache/CachePolicy.h"
+#include "core/loader/cache/CachedResourceInitiatorInfo.h"
 #include "core/platform/PurgePriority.h"
 #include "core/platform/Timer.h"
 #include "core/platform/network/ResourceError.h"
@@ -250,6 +251,9 @@ public:
 
     virtual bool canReuse(const ResourceRequest&) const { return true; }
 
+    const CachedResourceInitiatorInfo& initiatorInfo() const { return m_initiatorInfo; }
+    void setInitiatorInfo(const CachedResourceInitiatorInfo& initiatorInfo) { m_initiatorInfo = initiatorInfo; }

[Nate Chapin, 2013/05/15 22:14:58]

What is the rationale for moving this here from CachedResourceLoader? Not
opposed, just want to make sure I understand.

[abarth-chromium, 2013/05/15 22:21:25]

Previously CachedResourceLoader kept a HashMap keyed off CachedResource.  Given
that all CachedResources are initiated by something, that meant we had a HashMap
entry for all of them.  It's more efficient and more sensible to just store the
information in the CachedResource itself instead of in a look-aside HashMap.

+
 protected:
     virtual void checkNotify();
     virtual void finishOnePart();
@@ -354,6 +358,8 @@ private:
 
     // These handles will need to be updated to point to the m_resourceToRevalidate in case we get 304 response.
     HashSet<CachedResourceHandleBase*> m_handlesToRevalidate;
+
+    CachedResourceInitiatorInfo m_initiatorInfo;
 };
 
 }