Threading and Synchronization with the WebBrowswer control
- From: Norman Bullen <norm@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 25 Feb 2007 23:05:31 GMT
My application is built around an instance of the WebBrowser control. When I run it in the debugger, I see a number of threads created after my app calls the Navigate2() method.
My app is compiled and linked with the single threaded libraries and so far I haven't seen any problems as a result but I'm now concerned that there may be potential problems that I haven't seen yet.
Are the calls to my methods (including events based on IDispatch) guaranteed to be serialized? Are Windows messages used for this purpose? Is it possible for an event method be called after it has been unhooked by a call to Unadvise() because the event was triggered by code running asynchronously in one those other threads?
TIA for any thoughts on this.
Norm
--
--
To reply, change domain to an adult feline.
.
- Follow-Ups:
- Re: Threading and Synchronization with the WebBrowswer control
- From: Igor Tandetnik
- Re: Threading and Synchronization with the WebBrowswer control
- Prev by Date: Re: Cannot get frames in IHTMLDocument2 when first navigating to a page with iframes
- Next by Date: Re: Threading and Synchronization with the WebBrowswer control
- Previous by thread: Cannot get frames in IHTMLDocument2 when first navigating to a page with iframes
- Next by thread: Re: Threading and Synchronization with the WebBrowswer control
- Index(es):
Relevant Pages
|