Home/ Questions/Q 4241356
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T03:17:42+00:00

I’m making several HttpWebRequest.BeginGetResponse calls, and in the callback method of the BeginGetResponse ,

  • 0

I’m making several HttpWebRequest.BeginGetResponse calls, and in the callback method of the BeginGetResponse, I’m invoking an EventHandler. In the EventHandler, there is logic to test if the download was successful. If not, it tries to redownload the Html. I’m noticing lots of threads being generated especially when there are errors. So, on which thread do the Async Callbacks run?

Is there anyway I can invoke the EventHandler on the original thread? If that is not posible, can I invoke it on the UI thread?

Thanks!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Callbacks are made on a threadpool thread. There is no mechanism in .NET to make code run on a specific thread. That is very hard to come by, you can’t just interrupt a thread while it is busy and make it run some code. That causes horrible re-entrancy problems that a lock cannot solve.

    A thread must be in an idle state, not actively mutating the state of the program. There’s one kind of thread that behaves that way, the UI thread in a Winforms or WPF app. That’s also the thread that has to deal with objects that are fundamentally thread-unsafe, anything related to the UI. This is not a coincidence.

    Both class libraries make it possible to marshal a call from a worker thread to the UI thread, specifically to help getting the UI updated in a thread-safe way. In Winforms you use Control.Begin/Invoke(), in WPF you use Dispatcher.Begin/Invoke(). BackgroundWorker is a handy class to get this done without explicitly managing the marshaling. But isn’t suitable for I/O completion callbacks.

    • 0