Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Architecture for a Service with Multiple Clients using DispatcherObject
#1
Guys....this is hardcore programming... If you are no programmer/developer you may skip this now.

I just published an article describing an architecture for having multiple clients on a service where the clients are notified on it's own thread. It's more robust for finding problems later on. I'm using the DispatcherObject for holding the threads.

https://www.codeproject.com/Articles/115...-Clients-u
Cardano is the most promising 3 gen. crypto right now.


Reply
#2
(2016-12-04, 07:10 PM)Carsten Wrote: Guys....this is hardcore programming... If you are no programmer/developer you may skip this now.

I just published an article describing an architecture for having multiple clients on a service where the clients are notified on it's own thread. It's more robust for finding problems later on. I'm using the DispatcherObject for holding the threads.

https://www.codeproject.com/Articles/115...-Clients-u

I suppose this is useful for lots of applications that use grafical user interfaces.
They often get blocked when there are major changes.

It is true: it is kind of hardcore. I see i still have to learn a lot in programming. But I think  I see the logic in it.
What is this thing that builds our dreams, yet slips away from us?

Reply
#3
Yes, the GUI should not be interrupted by business logic.

Very good you took your time to see the logic in the architecture!
Cardano is the most promising 3 gen. crypto right now.


Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)
Banners