Let Chrome HTTP stack handle number of connections

First of changes based on willchan's feedback.

Note that this code doesn't really work as intended anyway.

Change-Id: I91d43f1daa78248700738338cf3d24a12496ac19

1 files changed, 7 insertions, 0 deletions

diff --git a/WebCore/platform/network/android/ResourceRequestAndroid.cpp b/WebCore/platform/network/android/ResourceRequestAndroid.cpp
index 7f4bccb..00735f3 100644
--- a/WebCore/platform/network/android/ResourceRequestAndroid.cpp
+++ b/WebCore/platform/network/android/ResourceRequestAndroid.cpp
@@ -30,10 +30,17 @@ namespace WebCore {
 
 unsigned initializeMaximumHTTPConnectionCountPerHost()
 {
+#if USE(CHROME_NETWORK_STACK)
+    // The chromium network stack already handles limiting the number of
+    // parallel requests per host, so there's no need to do it here.  Therefore,
+    // this is set to a high value that should never be hit in practice.
+    return 10000;
+#else
     // 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;
+#endif
 }
 
 } // namespace WebCore