In a previous post, I implemented a JobDispatcher using a queue and a BackgroundWorker. There are 3 simple JobDispatcher I'd like to implement now:
a NullJobDispatcher, that, basically does nothing, a SynchronousJobDispatcher, that execute the job when it is dispatched, a ReactorJobDispatcher, that uses the ThreadPool.
Read moreThe JobDispatcher has to tasks to perform: keeping track of the dispatched jobs and executing them.
So, at one point, Marc and I discussed about adding a virtual Execute(IJob job) method that would Execute the job. This way, inheritors could add tracking or exception handling.
Read moreThe JobDispatcher and the Jobs are a nice architecture because they follow two important principles of OO design, separation of concerns and inversion of control:
To go even further with the inversion of control, we could...
Read moreA while ago, a friend of mine blogged on commands and command dispatchers. After a "sure, why not" phase, I decided to give it a try for implementing a small application.
Read moreIn most cases, comparing two instances of the same time is considered to be an intrinsic feature of the type. This is true for int or DateTime. But what about a Person? Should we compare the Name or the DateOfBirth?
This is when the Comparer becomes handy. You can create one on your type for each scenario.