Set the target type when creating the request for main resource

Source/platform/network/ResourceRequest.cpp

Index: Source/platform/network/ResourceRequest.cpp
diff --git a/Source/platform/network/ResourceRequest.cpp b/Source/platform/network/ResourceRequest.cpp
index 02a0ec18bb5f63008d7a88322ea6dfa093c5e1a0..db0d026a28fb3c5abc0a96eb7efbe88fd40b4053 100644
--- a/Source/platform/network/ResourceRequest.cpp
+++ b/Source/platform/network/ResourceRequest.cpp
@@ -82,6 +82,12 @@ PassOwnPtr<CrossThreadResourceRequestData> ResourceRequest::copyData() const
     return data.release();
 }
 
+void ResourceRequest::initializeForMainResource(bool isMainFrame)

[ppi, 2014/06/19 18:25:42]

This can be called at any point, while ::initialize() has the nice property of
being private and called only from constructors.

There seems to be existing pattern here of setting additional parameters by
adding a specialized constructor that calls ::initialize() to set up defaults
first, and then overrides some of them, see "ResourceRequest(const KURL& url,
const Referrer& referrer ..." .

Would this pattern work for this case?

For overrides from content we could use simple setters (setTargetType /
setPriority).

+{
+    m_targetType = isMainFrame ? TargetIsMainFrame : TargetIsSubframe;
+    m_priority = ResourceLoadPriorityVeryHigh;
+}
+
 bool ResourceRequest::isEmpty() const
 {
     return m_url.isEmpty();