Thread A notifying Thread B of an Event

  • Thread starter Thread starter Bob Day
  • Start date Start date
Hi David,

Thanks for your answer,

What I did try to show in this thread is (the problem is not important
anymore) that there is chosen for a thread solution instead of a remoting
solution. There is a Main process, which starts two threads.

With "horizontal" solutions, I mean that the managing of the solution is not
ordered by a higher vertical level but done on the same process level.

However, it is worse, the solution is:
Main
- B
- A
B is doing the control part using timers, (I said before those timers is not
the most important of the bad design).

The solution could have been remoting (and than I agree, with all what you
say)
A B with control to each other

Or multithreading
Main (with control over A and B)
A B

What you said about what I should have said about the data process approach
I never said, in both situations it is in my opinion that the best (the
only) choose to use separated data, it would otherwise kill it self in
concurrency problems.

I hope this makes it clearer.

Cor
 
Back
Top