diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-24 01:29:20 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-10-24 01:29:20 +0000 |
| commit | 5778de6e6bfbc0439f49a245a75efa44e4f9a771 (patch) | |
| tree | 7596aff0328ee022a23a9a0e84c28f94ee40ea30 /chrome_frame/plugin_url_request.h | |
| parent | b5be3f53d7af0037dbc634beb550752de56ad840 (diff) | |
| download | chromium_src-5778de6e6bfbc0439f49a245a75efa44e4f9a771.zip chromium_src-5778de6e6bfbc0439f49a245a75efa44e4f9a771.tar.gz chromium_src-5778de6e6bfbc0439f49a245a75efa44e4f9a771.tar.bz2 | |
Currently the host network stack in IE which uses Urlmon interfaces to initiate
and complete URL downloads requested by ChromeFrame, executes in the UI thread of IE.
While this works fine in most cases for large data sizes, the IE UI thread ends up being
busy pulling the data in our IBindStatusCallback::OnDataAvailable implementation. As a result
the browser hangs until all data is pulled out.
The fix is to handle Urlmon requests on a separate thread.
This fixes http://code.google.com/p/chromium/issues/detail?id=24007
Changes to plugin_url_request.cc/.h are to set the LF property on these files.
Bug=24007
Review URL: http://codereview.chromium.org/292035
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@29986 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame/plugin_url_request.h')
| -rw-r--r-- | chrome_frame/plugin_url_request.h | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/chrome_frame/plugin_url_request.h b/chrome_frame/plugin_url_request.h index fb28c77..8c38b92 100644 --- a/chrome_frame/plugin_url_request.h +++ b/chrome_frame/plugin_url_request.h @@ -13,6 +13,7 @@ #include "net/base/upload_data.h" #include "net/url_request/url_request_status.h" #include "base/ref_counted.h" +#include "chrome_frame/chrome_frame_delegate.h" class PluginUrlRequest; @@ -52,7 +53,7 @@ class PluginUrlRequest : public UrlRequestReference { // These cookies are sent when we receive a response for every URL request // initiated by Chrome. Ideally we should only send cookies for the top level // URL and any subframes. However we don't receive information from Chrome - // about the context for a URL, i.e. whether it is a subframe, etc. + // about the context for a URL, i.e. whether it is a subframe, etc. // Additionally cookies for a URL should be sent once for the page. This // is not done now as it is difficult to track URLs, specifically if they // are redirected, etc. |