Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The value in <code>BackgroundWorker</code> is that it can raise its <code>ProgressChanged</code> and <code>RunworkerCompleted</code> event on the thread that created its instance. Which makes it <em>very</em> convenient in programs that cannot support free threading.</p> <p>For this to work properly, it is however required that the <code>SynchronizationContext.Current</code> property references a non-default synchronization provider. A provider which is responsible for marshaling calls from one thread to another. The .NET framework has two providers that are readily available: <code>System.Windows.Forms.WindowsFormsSynchronizationContext</code> and <code>System.Windows.Threading.DispatcherSynchronizationContext</code>. These providers handle synchronization for, respectively, Winforms and WPF.</p> <p>There's a connection, Winforms and WPF are both class libraries that have a threading problem. Both implement GUIs and Windows based graphical user interfaces are fundamentally thread-unsafe. Windows windows can only be updated from the thread that created them. In other words, these custom synchronization providers exist because there's a dire need for them. Also notable is that they work by taking advantage of the way UI threads work. A UI thread executes code in an event driven way, pumping a message loop to receive notifications. The synchronization provider can inject calls to event handlers using this mechanism. This is no accident.</p> <p>Back on topic, a Windows service has no such facility. It doesn't have a GUI and doesn't install a custom synchronization provider. As such, <code>BackgroundWorker</code> provides no feature that's useful in a service. Without the custom synchronization provider, the default provider simply runs events on a threadpool thread. Which is not useful, you might as well fire the event from your worker thread. Getting events to run on another specific thread is very difficult to achieve, unless you recreate the message loop mechanism or hook into the Winforms plumbing and create a simulated UI thread using an invisible window. Which is not entirely uncommon btw.</p>
    singulars
    1. This table or related slice is empty.
    1. POMultithreaded service, BackgroundWorker vs ThreadPool?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USWai Ha Lee
    1. USHans Passant
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMultithreaded service, BackgroundWorker vs ThreadPool?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSo BackgroundWorker internally runs under a ThreadPool in my service and I would get pretty much the same result if I switch from BackgroundWorkers to ThreadPool?
      singulars
      1. PO
      1. USbevacqua
    2. COYes, you don't get the value add in a service.
      singulars
      1. PO
      1. USHans Passant
    3. COEverything runs under the CLR thread pool nowadays anyway.
      singulars
      1. PO
      1. UShoodaticus
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload