Implement our own parallel connection count initialization.

Use 20 since we have 4 connection threads that can pipeline up to 5 requests per
thread.

2 files changed, 9 insertions, 1 deletions

diff --git a/WebCore/platform/network/ResourceRequestBase.cpp b/WebCore/platform/network/ResourceRequestBase.cpp
index bfa3dc6..f9ecb6b 100644
--- a/WebCore/platform/network/ResourceRequestBase.cpp
+++ b/WebCore/platform/network/ResourceRequestBase.cpp
@@ -355,7 +355,7 @@ void ResourceRequestBase::updateResourceRequest() const
     m_resourceRequestUpdated = true;
 }
 
-#if !PLATFORM(MAC) && !USE(CFNETWORK)
+#if !PLATFORM(MAC) && !USE(CFNETWORK) && !PLATFORM(ANDROID)
 unsigned initializeMaximumHTTPConnectionCountPerHost()
 {
     // This is used by the loader to control the number of issued parallel load requests. 
diff --git a/WebCore/platform/network/android/ResourceHandleAndroid.cpp b/WebCore/platform/network/android/ResourceHandleAndroid.cpp
index 3d9b576..d67bc2b 100644
--- a/WebCore/platform/network/android/ResourceHandleAndroid.cpp
+++ b/WebCore/platform/network/android/ResourceHandleAndroid.cpp
@@ -148,4 +148,12 @@ void ResourceHandle::loadResourceSynchronously(const ResourceRequest& request,
     client->webFrame()->startLoadingResource(&h, request, true);
 }
 
+unsigned initializeMaximumHTTPConnectionCountPerHost()
+{
+    // This is used by the loader to control the number of parallel load
+    // requests. Our java framework has 4 threads that can each pipeline up to
+    // 5 requests. Use 20 as a maximum number.
+    return 20;
+}
+
 } // namespace WebCore