DownloadRequestAsynch, ProtocolHandlerDataFullyRead and similar called with wrong sender

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Add 2 csExWB controls and attach the same DownloadRequestAsynch or
ProtocolHandlerDataFullyRead events
2. Programatically navigate with the first one to any page
3. Check that the "sender" parameter is the expected one of the browsers

What is the expected output? What do you see instead?
When navigating with browser1 those functions (and probably the other like
them) are called with the "sender" parameter set to browser2. Other events
like BeforeNavigate2, DocumentComplete, etc. are not affected.

What are the OS and IE versions?
Windows XP Pro SP3, IE7.

What version of the product are you using?
2.0.0.2

Please provide any additional information below.

Original issue reported on code.google.com by manixr...@gmail.com on 1 May 2009 at 2:31

[GoogleCodeExporter]

More testing shows that adding more controls will always call those events with 
the
last control added.

Original comment by manixr...@gmail.com on 1 May 2009 at 3:12

[GoogleCodeExporter]

Apparently there is a way to solve this, I have found this:
http://www.blackfishsoftware.com/blog/don/passthroughapp_bho_toolbar_interceptin
g_requests_responses

(csexwb2 uses the same passthroughapp method)

I have tried extracting a normal function from Google gears source code, but I 
have a
very limited time and understanding of the code.

As far as my understanding goes, the function StartImpl in http_handler_base.cc 
is
the implementation of both StartEx and Start (see http_handler_app.cc), both of 
which
are called and later calls the StartImpl.

Can anybody understand how to make the necessary changes to avoid the 
frustrating bug?

Thanks in advance!

Original comment by AviEli...@gmail.com on 20 Jul 2009 at 6:59