Databases
StackOverflow2013
Postsdbo
POIs WPF Dispatcher the solution of multi threading problems?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIs WPF Dispatcher the solution of multi threading problems?
    primarykey
    data
    text
    <p>I have a very bad feeling about using lock in my code but now the Dispatcher of WindowBase exists and I want to use it everywhere.</p> <p>For example I use a multi thread singleton WCF service who publish events on the EventAggregator of PRISM, the payload is immutable (it is just data) and every thread with a dispatcher can retrieve the event gracefully, whitout deadlock in their own dispatcher. (Not only UI thread, but also threads with database calls, threads with services call, threads which log or other threads with slow calls, because I don't want to freeze the UI).</p> <p>But my problem is that this Dispatcher is coupled with WPF so I feel a bit guilty when I use it everywhere, I feel that the dispatcher was not created for my use case in mind.</p> <p>Does it exist another Dispatcher implementation not coupled with WPF ? or that's OK to abuse it ?</p> <p>Thanks,</p> <p><strong>Update</strong></p> <p>The solution that Paul Stovell give to me is to create an interface IDispatcher, and an adapter for the Wpf Dispatcher, so this will be easier to test ! This solution was good for me because, I refactored my tests and I can now use a SynchronousDispatcherAdapter in my tests (Thanks to it, I don't have to use the Dispatcher of WPF in my tests).</p> <p>Using the Dispatcher instead of a BackgroundWorker make sense, because I'm using a multi publisher / subscriber pattern (with PRISM), and thanks to the Dispatcher every event handler are called on threads who subscribe them to the event. This means that the only point where multi threading issue can happen is at the payload of my event (I made him immutable).</p> <p>My different threads don't communicate directly between them they can just publish and subscribe to event. Thus, database calls, logs calls, services calls, UI calls run on different threads and don't know about each other (they only know about events they subscribe and publish).</p> <p>The background worker will make sense, when I will make some calls from my UI to a repository.</p> <p>But I hope to find a design without using BackgroundWorker because I prefere to use this subscriber/publisher pattern (I think it makes my code more readable)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USNicolas Dorier
    1. USNicolas Dorier
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIs WPF Dispatcher the solution of multi threading problems?
      1. USErik Hellström
      1. VTFavorite
    2. VO
      singulars
      1. POIs WPF Dispatcher the solution of multi threading problems?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POIs WPF Dispatcher the solution of multi threading problems?
      1. USDavid Schmitt
      1. VTFavorite
    1. This table or related slice is empty.
 

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